What Are Webhooks?
Webhooks let Hedy send data to other apps and services in real time. When an event occurs — like a session ending or a highlight being created — Hedy sends the data to a URL you specify. This lets you build powerful automations without any coding.
For example, you could automatically:
Save meeting transcripts to Google Docs or Notion
Post session recaps to a Slack channel
Create tasks in Asana or Todoist from action items
Log session data to a spreadsheet
Requirements
Hedy Pro subscription — Webhooks are a Pro feature
Cloud Sync enabled — Required so Hedy can process webhook events through the cloud
You can view your webhooks without Cloud Sync, but you need it enabled to create, edit, or trigger them.
Setting Up a Webhook
Open Hedy and go to Settings
Scroll down to the API Access section
Tap Manage Webhooks
Tap the + button to add a new webhook
Enter a name (optional) — a label to help you remember what this webhook is for (e.g., "Zapier — Meeting Notes")
Paste the webhook URL from your external service — this must be an HTTPS URL
Select the events you want to subscribe to (see below)
Tap Create
You can create up to 10 webhooks.
Available Events
Choose which events trigger your webhook:
Session Created — Fires when you start a new recording. Sends the session title and start time.
Session Ended — Fires when a recording finishes. Sends the full session data including transcript, recap, meeting minutes, highlights, and topic information. This is the most comprehensive event.
Session Exported — Fires when you manually export a session to your webhooks. Sends similar data to Session Ended (transcript, recap, highlights, etc.).
Highlight Created — Fires each time a highlight is captured during a session. Sends the highlight text, AI insight, and timestamp.
Todo Exported — Fires when you export an action item. Sends the todo text, due date, and associated session.
Exporting a Session Manually
In addition to automatic events, you can manually send any session to your webhooks:
Open a completed session
Tap Export to Webhook
If you have multiple webhooks subscribed to the Session Exported event, select which ones to send to
Confirm the export
Testing Your Webhook
Before relying on a webhook, you can verify it works:
Go to Settings > API Access > Manage Webhooks
Tap the test button on any webhook
Hedy sends a test payload to your URL and shows whether it succeeded, along with the response status code
If the test fails, double-check that the URL is correct and that your external service is ready to receive requests.
What Data Is Sent?
Every webhook request is an HTTP POST with a JSON body. The data depends on the event type, but a Session Ended event includes:
Session details — Title, start time, end time, duration
Transcript — The full text of your session
Conversations — Structured speaker-by-speaker dialogue
Meeting minutes — Key discussion points
Recap — AI-generated summary
Highlights — Each highlight with its AI insight, quote, and timestamp
Topic — The topic name and insights, if the session is assigned to a topic
Security & Verification
Every webhook request includes a signature so you can verify it genuinely came from Hedy:
X-Hedy-Signature header — An HMAC-SHA256 hash of the request body, signed with your webhook's unique secret
X-Hedy-Event header — The event type (e.g., session.ended)
All webhook URLs must use HTTPS to ensure your data is encrypted in transit. Hedy will not send data to HTTP endpoints.
Using Webhooks with Popular Platforms
Zapier — Create a Zap with "Webhooks by Zapier" as the trigger. Choose "Catch Hook," copy the webhook URL, and paste it into Hedy.
Make (formerly Integromat) — Add a "Custom Webhook" module as your scenario trigger. Copy the generated URL and paste it into Hedy.
n8n — Add a "Webhook" trigger node to your workflow. Copy the production URL and paste it into Hedy.
Delivery & Retries
Hedy automatically retries failed deliveries:
Server errors (5xx) — Retried up to 2 times with increasing delays
Rate limited (429) — Retried once, respecting the service's retry timing
Client errors (4xx) — Not retried, as these typically indicate a configuration issue
Troubleshooting
Webhook test fails — Verify the URL is correct, uses HTTPS, and that your external service is actively listening for requests.
Not receiving events — Check that Cloud Sync is enabled, the webhook is subscribed to the correct event, and that your Pro subscription is active.
"Webhooks require Pro" message — Upgrade to Hedy Pro in Settings > Subscription to access webhooks.
"Cloud Sync required" message — Enable Cloud Sync in Settings > Cloud Sync, or tap the Enable button on the warning banner shown at the top of the Webhooks screen.
Pro tip: Start by subscribing to the Session Ended event — it includes the most comprehensive data and is the most useful for building automations around your meeting notes.