Send a finished call transcript into SAGARIS
Yes, in one direction, for any recorder that can send a webhook. A finished transcript is pushed into SAGARIS, which archives the recording against the contact it belongs to, marks the meeting as having happened, and runs the post-call work against it exactly as it would for a call placed in SAGARIS. Fireflies and Gong are the two whose native payload shapes are mapped in full. SAGARIS never calls out to any of them.
Inbound only. Your recorder pushes to SAGARIS and SAGARIS never calls your recorder. We hold no credential of yours for any of them, and the push is authenticated with a token you generate and can rotate.
Last verified October 5, 2026. All integrations
What moves, and which way
Inbound webhook, authenticated with a per-workspace token you generate and can rotate. No credential of yours is held.
- Into SAGARIS
- A finished transcript: the title, when it started, the participants, and the sentences with their speakers and timings. Fireflies' and Gong's own native field names are detected and mapped onto the shape SAGARIS uses before anything else happens, so neither needs reshaping by hand; anything else sends the documented normalized shape. On arrival the participants are resolved to contacts by email inside your workspace, the recording is archived against that record, the meeting is marked as having happened, and the intelligence work runs.
- Back into Fireflies, Gong and other call recorders
- Nothing, to any of them. There is no write path back into a recorder, no API key of yours held on our side, and no attempt to keep two systems in step. What you see in Fireflies or Gong stays exactly as that product left it.
- The boundary
- The push has to carry the transcript itself. A webhook that carries only a meeting or call id, expecting the receiver to fetch the body afterwards, needs a fetch adapter that is not built, so a sender shaped that way delivers nothing usable. This is the single most common reason a Gong setup appears connected and produces no transcripts, because an id-only notification is a shape Gong can send. Put an automation step in between that fetches the transcript with your own key and forwards the whole payload. A missing or unknown token is refused with a 401 and no partial write, so a misconfigured sender fails loudly rather than quietly filling a workspace with orphaned meetings.
Setting up the push
- 01
Generate the workspace webhook token
It lives in Settings, is scoped to your workspace alone, and can be rotated whenever you want. The rotation is recorded in the workspace configuration audit trail, so a credential change is something an admin can see afterwards.
- 02
Point a sender at the receiver
The destination is the SAGARIS transcript receiver with your token on the query string. Anything that can send a webhook can be the sender: the recorder directly if your plan allows it, or an automation tool sitting in between. There is nothing to install on either side.
- 03
Confirm the transcript body travels with the notification
This is the step that decides whether any of it works. If what your recorder sends is an id and a link, add a step that calls the recorder with your own key, fetches the transcript, and forwards the full payload. A Fireflies or Gong native payload carrying the sentences needs no reshaping; anything else should be sent in the documented normalized shape.
- 04
Check the first delivery landed on the right record
Matching is by participant email inside your workspace. A meeting whose attendees are not contacts yet archives without attaching to a record, which is usually the first thing worth fixing and is not a failure of the push.
Zoom, Otter, Teams and everything else
The receiver is recorder-agnostic, so any of them can reach it. What they do not get is the native-shape mapping: only Fireflies' and Gong's own field names are detected and renamed automatically. For anything else, an automation tool reshapes the payload into the documented normalized shape and posts it. That is a real path and we would be overstating it to list those products as connections, which is why they are named here rather than in a heading.
For calls placed through the SAGARIS dialer none of this applies. The call is recorded, transcribed, scored against a published rubric and written to the record with no second tool in the path, and the coaching rail runs while the call is still happening rather than after it. This webhook exists for the conversations that happen somewhere else, which for most teams means the video meetings a dialer never sees.
So the useful split, if you are keeping a recorder, is usually that it covers video meetings and SAGARIS covers the phone, with this webhook putting both on one timeline. That way the follow-up an agent drafts after a video call is grounded in what was actually said on it.
How we checked
Read from the receiver route and its importer rather than from a probe, because the endpoint is authenticated per workspace and probing it anonymously would prove only that the auth works. src/app/api/webhooks/transcripts/route.ts documents the accepted push shape, states that a missing or unknown token returns 401 with no writes, and records that a vendor whose webhook carries only an id needs a fetch adapter this receiver does not provide. src/lib/transcript-import.ts declares exactly two vendor shapes beside the normalized one, fireflies and gong, which is what bounds the claim on this page. Re-read on October 5, 2026, unchanged from September 18.
Verified October 5, 2026. If this is out of date or wrong, email founders@sagaris.ai and we will correct it and move the date.
Fireflies, Gong and other call recorders and SAGARIS, the questions people actually ask
- MOST ASKED
No. The direction is the other way for every recorder. SAGARIS holds no credential of yours for any of them and never calls their APIs. Your recorder, or something on your side, pushes the finished transcript to SAGARIS.
Not on its own, and this is the most common reason a setup looks connected and delivers nothing. The receiver takes an already-fetched transcript, and the adapter that would collect a body from a vendor API is not built. Add an automation step that fetches the transcript with your own Gong key and forwards the full payload.
Any that can send a webhook. Fireflies and Gong are the two whose own field names are detected and mapped automatically, so their native payloads work unchanged. Zoom, Otter, Teams and the rest reach the same receiver through an automation tool that reshapes the payload into the documented normalized shape.
Participants are resolved to contacts by email within your workspace, the recording is archived against that record, the meeting is marked as having happened, and the post-call intelligence runs against the transcript exactly as it would for a call placed in SAGARIS.
With an opaque token scoped to your workspace, on the query string. A missing or unknown token is refused with a 401 and no writes are performed. You can rotate the token from Settings and the rotation is recorded in the configuration audit trail.
No. Plenty of teams keep a recorder for video meetings and run SAGARIS for the phone, the CRM and the follow-up. This webhook is what puts both kinds of conversation on the same timeline. If the question is whether to replace it rather than how to connect it, the Gong comparison page linked below argues that case openly.
Next door