Meeting Transcription with Webhooks (2026)

Why webhooks for meeting transcription

Meeting transcripts are useful. Meeting transcripts that automatically flow into the right system are transformative. Most meeting notetakers trap your data in their own interface — a web dashboard you have to check, an inbox you have to process, a tab you forget.

Webhooks change the model. When a meeting ends and the transcript is ready, Resonant sends a POST request to your configured endpoints with the full payload. From there, your automation takes over:

• CRM logging. Push meeting summaries and key points to Salesforce, HubSpot, or Pipedrive opportunity records.
• Slack digests. Drop meeting summaries into a team channel automatically after every call.
• Notion databases. Create a new page in your meeting notes database with the full transcript.
• Custom backends. Feed transcripts into your own search index, AI pipeline, or analytics system.
• Zapier / Make. Use webhook triggers to connect to 5000+ apps without writing code.

How Resonant webhooks work

Resonant processes meeting audio locally on your Mac. When a meeting recording ends and transcription completes, it fires an HTTP POST to each configured webhook URL. The payload includes:

• Transcript text. The full meeting transcript with timestamps.
• Meeting metadata. Duration, start time, detected conferencing app (Zoom, Meet, Teams, etc.).
• Summary. AI-generated meeting summary with key points and action items (Pro feature).
• Speaker labels. Identified speakers when diarization is available.

Local processing, flexible output

The key difference from cloud meeting tools: transcription still runs entirely on your Mac. Audio never leaves the device. Webhooks are opt-in — you explicitly configure where transcript textgoes after processing. If you don't set up webhooks, nothing leaves your machine.

This is the best of both worlds: the privacy of local processing with the productivity of automated pipelines. You control the boundary — audio stays local, text goes where you want it.

Example: Sales call → CRM

A sales rep finishes a discovery call on Zoom. Resonant has been transcribing locally the entire time. The call ends. Within seconds, a webhook fires to the team's backend, which:

1. Extracts action items and next steps from the transcript
2. Matches the meeting to a Salesforce opportunity by participant email
3. Logs the call summary to the opportunity timeline
4. Posts a digest to the #sales-calls Slack channel

No manual note entry. No copy-paste. No cloud meeting bot that made the prospect uncomfortable.

Compared to cloud meeting APIs

Cloud tools like Fireflies, Otter, and Read.ai also offer webhooks and APIs. The difference:

• Cloud tools upload your audio to their servers first, process it there, then send you the result via webhook. Your meeting audio lives on their infrastructure.
• Resonant processes audio locally, then sends only the transcript text via webhook. Audio never touches a third-party server. You choose what leaves your machine.

Related resources

• AI agent access via MCP— let AI assistants query your meeting notes directly.
• Automatic meeting notetaker for Mac— how the capture and transcription works.
• Private meeting transcription— the privacy architecture explained.

Frequently asked questions