Integrating Sybill with your existing tools is easier than ever, thanks to webhooks. These enable seamless automations by sending Sybill data directly to other apps or automation platforms like Zapier or Make. With Sybill's webhook functionality, you can automatically send meeting summaries, action items, key insights, and deal stage changes to your team's preferred tools, keeping your workflows smooth and organized.
What are webhooks?
Webhooks are automated messages triggered by specific events and sent from one app to another in real time. Unlike traditional APIs that require constant polling to check for updates, webhooks notify your chosen application instantly when something important happens. For example, when a meeting finishes processing in Sybill, the webhook immediately sends that information to your selected tool.
Available webhook events
Sybill currently supports three webhook events:
Event | What it sends |
meeting.new_recording.v1 | The original meeting event: metadata, summary, participant insights, transcript, and CRM info for each newly processed recording. Existing v1 subscriptions keep working unchanged. |
meeting.new_recording.v2 | The complete conversation package in one payload: summary, transcript, participants, CRM matches, and recording links, in the same shape as the conversation returned by Sybill's public API. No follow-up API requests needed. |
deal.stage_changed.v1 | An instant notification when a deal moves stages in your CRM (for example, Discovery to Negotiation). Includes the full deal snapshot and the previous and new stage, using your organization's own stage names. |
You can subscribe an endpoint to one or more events from your webhook settings. The deal stage event unlocks automations such as Slack deal-room alerts, forecast updates, and RevOps workflows that react to pipeline movement in real time.
Managing webhooks in Sybill
Webhooks live under Settings > Integrations > Webhooks:
Click Add webhook to create a new one.
Each webhook in the list shows an on/off toggle, when it was last updated, who created it, and its error rate, so you can monitor delivery health at a glance.
The Docs link on this page opens the developer documentation.
Customizable automation
Not every meeting requires the same treatment, and Sybill's webhook automation lets you tailor which meetings trigger a webhook. You can set parameters such as meeting participants, topics, meeting types, and deal stages to ensure only relevant data is sent to your connected apps. This ensures your systems stay organized, avoiding information overload.
How to set up a webhook
There are two ways to go about it: through an intermediary such as Zapier or Make, or by creating your own endpoint.
Using intermediaries like Zapier or Make
Zapier and Make act as intermediaries that help you connect Sybill to thousands of other applications. They receive webhooks when your app of choice might not do so, and then send the information onward.
Start with Sybill:
Navigate to Settings > Integrations > Webhooks and click Add webhook. The setup involves three easy steps:
Name and describe the webhook: This helps you and your team understand what it does at a glance.
Choose the webhook event and define the trigger: Pick the event you want to receive. For meeting events you can send all meeting summaries or filter meetings based on specific criteria such as participants, topic trackers, meeting type, and deal parameters.
Set the destination URL: Paste the URL where you want the information to be sent.
Generate the destination URL in Zapier:
Log in to your Zapier account and click on Create Zaps.
Click on Trigger, then search for and select Webhooks by Zapier.
For Event choose Catch Hook and click Continue. Leave the Child Key empty.
Copy the webhook URL Zapier generates. You will need it in the next step.
Connect Zapier and Sybill:
Return to Sybill and paste the URL in the last step of creating the new webhook. Click Create.
Hover over the webhook you just created and click Test to send a test payload to Zapier.
In Zapier click Test Trigger to find the test payload, select it, and click Continue with selected record. A successful payload test confirms the connection is established.
Quick tip: You can maintain a 'Private List' of meetings in Sybill, which will exclude those meetings from being shared through the webhooks you create even if they pass through the filtering. This helps protect sensitive or private information. To create your Private List, go to Call Sharing in Sybill Settings.
From this point forward, the next steps depend on your specific use case: identify the relevant portion of the payload received from Sybill, and determine which fields in your app should be updated with this information. Zapier's looping features are helpful when you want to act on each participant in a meeting, for example to update the pain points and interests of each meeting participant in your CRM.
Creating your own endpoint to receive webhooks
At their core, webhooks are just POST requests sent to a designated endpoint, essentially a URL that listens for incoming event data.
Choose your endpoint: Decide where you want to receive webhook data (for example, https://yourapp.com/sybill-webhooks). A unique URL per service is recommended.
Configure your listener: Ensure it handles POST requests, disable CSRF protection for this route if applicable, and aim to respond within 15 seconds with a 2xx status code.
Security first: Implement signature verification and check timestamps to prevent replay attacks.
Select your events: Subscribe the endpoint to meeting.new_recording.v1, meeting.new_recording.v2, and/or deal.stage_changed.v1 in your webhook settings.
Test and verify: Use the Test button to send sample webhooks, then monitor delivery and troubleshoot as needed.
Webhook signature verification
For security, it's essential to verify that the webhooks you receive are actually coming from Sybill. Our partner, Svix, offers libraries to make this process easy. By verifying webhook signatures and timestamps, you can be confident in the authenticity of the messages you're processing. The signing secret can be found on Sybill's dashboard when you click on the key icon next to your endpoint.
Handling webhook retries
In case of delivery failure, Svix implements a retry system with exponential backoff. If a webhook delivery attempt fails, it is retried on the following schedule: immediately, after 5 seconds, 5 minutes, 30 minutes, 2 hours, 5 hours, then 10 hours (with additional 10-hour intervals thereafter). If an endpoint is removed or disabled, the retries stop.
Payload schemas
Every event envelope contains an eventId, eventType, eventVersion, timestamp, objectId, objectType, and a data object with the event contents.
meeting.new_recording.v1: data includes crmInfo (account and opportunity), metadata (title, platform, start time, duration, participants), participantInsights (interests and pain points per participant), summary (outcome, key takeaways, next steps, conversation starters), and the transcript.
meeting.new_recording.v2: data carries the full conversation object in the same shape as Sybill's public API returns for a conversation, so you can process it without any follow-up API calls.
deal.stage_changed.v1: data carries the full deal snapshot plus the previous and new stage using your organization's stage names.
For complete schemas, example payloads, and API conventions, please see Get started with the Sybill API and API pagination, rate limits, errors, and conventions.
FAQs
I already use meeting.new_recording.v1. Do I need to migrate?
No. Existing v1 subscriptions keep working unchanged. Subscribe to v2 whenever you want the richer payload.
Who can use webhooks?
Webhooks are available on plans with API access, and enabling them is self-serve from webhook settings.
Will I receive duplicate notifications?
No. Sybill's webhook delivery pipeline deduplicates notifications, including when CRM syncs retry or re-check, and does not send stale notifications from historical backfills.