Overview
Webhooks V2 provides an improved webhook system with granular event subscriptions and enhanced security. You can subscribe to specific meeting lifecycle events and receive real-time notifications at your configured endpoint.Webhooks V2 replaces the legacy webhook system. If you are currently using Webhooks V1, we recommend migrating to V2 for a better experience.
Events Supported
Webhooks V2 supports the following events:You can subscribe to one or more events per webhook. Only events you subscribe to will be delivered.
Setting Up Webhooks V2
1
Visit the Webhooks V2 configuration page
2
Enter a valid HTTPS URL that accepts POST requests in the Webhook URL field
3
Optionally, enter a Signing Secret for payload signature verification
4
Select the events you want to subscribe to
5
Save your configuration
Webhook Payload
Each webhook notification is sent as aPOST request with a JSON payload containing the following fields:
The event type that triggered the webhook (e.g.,
meeting.transcribed, meeting.summarized, meeting.bot_joined)Unix timestamp in milliseconds indicating when the event was fired
Identifier for the meeting that the event relates to. This is the same as the transcript ID used throughout the Fireflies API.
Custom identifier set by you during upload. Use this to correlate webhook events with your uploads.
Example Payloads
Meeting TranscribedWebhook Authentication
Webhooks V2 uses HMAC-SHA256 signatures to verify that webhook payloads originate from Fireflies and have not been tampered with in transit.How It Works
Each webhook request includes anX-Hub-Signature header containing a SHA-256 HMAC signature of the request body. The signature is computed using the signing secret you configured during setup.
The signature format is:
Verifying the Signature
1
Extract the
X-Hub-Signature header from the incoming request2
Compute the HMAC-SHA256 digest of the raw request body using your signing secret
3
Prefix the hex-encoded digest with
sha256=4
Compare the computed signature with the header value using a timing-safe comparison
Verification Examples
Request Headers
Each webhook delivery includes the following headers:Delivery Behavior
- Webhooks are sent as
POSTrequests to your configured URL - Your endpoint must respond with a
2xxstatus code within 10 seconds to be considered successful - If your endpoint does not respond in time or returns a non-
2xxstatus code, the delivery is marked as failed
Migrating from Webhooks V1
If you are using the legacy webhooks system, here is a summary of the key differences:Migration Steps
1
Go to the Webhooks V2 setup page
2
Enter your existing webhook URL
3
If you used a signing secret, enter it in the Signing Secret field
4
Select the events you want to subscribe to (choose
meeting.transcribed for equivalent V1 behavior)5
Save and update your webhook consumer to handle the new payload format and signature header
FAQ
What is the difference between meeting.transcribed and meeting.summarized?
What is the difference between meeting.transcribed and meeting.summarized?
meeting.transcribed fires when the raw transcript is ready and available for viewing. meeting.summarized fires after the AI-generated summary (including action items, notes, and other insights) has been processed.What is meeting.bot_joined used for?
What is meeting.bot_joined used for?
meeting.bot_joined fires when the Fred bot successfully joins a meeting. This is useful for triggering real-time streaming workflows as soon as the bot is in the call.Can I subscribe to multiple events?
Can I subscribe to multiple events?
Yes. You can select one or more events during setup. Only events you subscribe to will trigger webhook deliveries.
Why am I not receiving webhook notifications?
Why am I not receiving webhook notifications?
- Webhooks are only fired for meetings you own (i.e., you are the
organizer_email). - Ensure your endpoint accepts POST requests and responds with a 2xx status code within 10 seconds.
- Verify that you have subscribed to the correct events.
- If using signature verification, ensure your signing secret matches what is configured.
Do I need to migrate from Webhooks V1?
Do I need to migrate from Webhooks V1?
Webhooks V1 continues to work. However, V2 offers granular event subscriptions, so we recommend migrating when convenient.
Additional Resources
Webhooks V1
Legacy webhook documentation
Upload Audio
Use the API to upload audio to Fireflies.ai