Skip to main content

Configure your webhook in Rafiki AI Settings

Step-by-step guide to enabling and testing webhook delivery in Rafiki AI.

Written by Jake from Rafiki.ai

Configure your webhook in Settings

Once you have a webhook URL from Zapier, Make, n8n, or your own server, follow these steps to activate webhook delivery in Rafiki AI.

Step-by-step setup

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

  2. Go to Settings → Webhooks

  3. Toggle on Enable webhook delivery

  4. Paste your URL into the Webhook URL field

  5. (Optional) Copy the auto-generated Signing Secret — save this somewhere secure if you plan to verify signatures on your server

  6. Under Include in payload, choose which fields Rafiki AI should send:

    • Meeting summary — the AI-generated summary notes

    • Full transcript — the complete speaker-segmented transcript

  7. Click Save

Verify your setup with a test webhook

  1. After saving, click the Test Webhook button

  2. Rafiki AI sends a sample payload to your URL immediately

  3. A success or failure banner appears with the HTTP response code

  4. Check your destination to confirm the test payload arrived

Tip: The test payload uses the event type webhook.test instead of meeting.completed, so you can filter test data out if needed.

Managing your webhook

  • Pause deliveries: Toggle off Enable webhook delivery. Your URL and secret are saved for later.

  • Change destinations: Edit the URL and save — no other changes needed.

  • Regenerate signing secret: Click Regenerate next to the secret field. Update your server/automation tool with the new secret afterward.

  • Disable a customer field: Uncheck it under "Include in payload" and save.

When webhooks fire

Rafiki AI sends the webhook after the meeting is fully processed:

  1. Call ends and recording is captured

  2. Rafiki AI transcribes the audio

  3. AI generates the summary, topics, trackers, and analytics

  4. ➜ Webhook fires with full data

This means you get the summary and transcript in the same payload — you don't need to poll for updates or wait separately.

Did this answer your question?