Skip to main content

Getting started with Auto-Export Webhooks

What webhooks are, what you can do with them, and how to get started.

Written by Jake from Rafiki.ai

What are Auto-Export Webhooks?

Webhooks let Rafiki AI automatically send your meeting data — summary, transcript, attendees, and more — to any external system after each call is processed. You configure one URL, and Rafiki AI POSTs meeting data to it every time a call wraps up.

Connect this to Zapier, Make, n8n, or your own server to route meeting data anywhere: Google Drive, Notion, Google Sheets, Slack, your CRM, or any other app.

What you can do with Webhooks

  • Auto-save transcripts to Google Drive — one Google Doc per call, created automatically

  • Log calls to a Google Sheet — a new row per meeting with title, date, host, summary

  • Push summaries to Notion — create a page in your CRM database for each call

  • Notify your team in Slack — post meeting summaries to a channel after each call

  • Sync to your CRM — add call notes as activities on deals or contacts

  • Trigger any automation — use the webhook as the starting point of any workflow in 5,000+ apps

How to access Webhooks

  1. Log in to Rafiki AI at app.getrafiki.ai

  2. Click Settings in the left sidebar

  3. Select the Webhooks tab

Note: Only users with admin access can configure webhooks. The webhook applies to your whole Rafiki AI account — all meetings processed in your workspace will fire the webhook.

What you'll need

  • A webhook URL to send data to. Most customers get this from Zapier (free tier available) or Make. You can also use your own server.

  • A destination in mind (Google Drive folder, Notion database, Sheet, etc.)

  • About 5 minutes to set up your first integration

How it works

After each meeting is recorded, transcribed, and analyzed by Rafiki AI's AI, the system sends a POST request to your configured webhook URL containing the meeting data. You then route that data to your destination of choice.

Rafiki AI waits until processing is complete before firing the webhook — so the payload always includes the full summary and transcript, not just the raw recording.

Did this answer your question?