Feedback source
Turn sales-call transcripts into ranked product insight
The reasons deals stall get said out loud on calls and written down nowhere countable. Forward your transcripts and the recurring ones become ranked topics.
Why connect Call transcripts
- Capture what loses deals. A missing feature mentioned on nine calls is a ranked topic instead of a hunch someone repeats in a meeting.
- One integration, three vendors. Gong, Fireflies, and Granola all work through the same endpoint.
- Weighted by who said it. The call host's email is captured, so transcripts can be matched to accounts.
"Export keeps timing out on large projects, this is blocking our team."
Deduped and ranked alongside every other source.
How it works
- 1
Pick a shared secret
Any long random string. Paste it into the transcripts card.
- 2
Add a webhook or automation
In Gong, Fireflies, or Granola, point it at the ingest URL.
- 3
Watch it triage
Transcripts become feedback items, grouped and ranked by AI.
Prefer the full walkthrough? Read the Call transcripts setup guide.
Before you start
- A call-recording tool that can send a webhook or run an automation: Gong, Fireflies, and Granola all can, directly or through Zapier.
- A FeedbackFlow project. The free plan covers one, and no credit card is needed to finish this setup.
- A decision about which calls to send. Every sales call is usually too many; a customer-discovery or churn-interview subset is usually the useful part.
How to connect Call transcripts to FeedbackFlow
- 1
Choose and save a shared secret
Pick any long random string and paste it into the call-transcripts card in your FeedbackFlow project settings. None of these vendors signs its webhooks in a way we can verify uniformly, so the secret in the URL is what proves a delivery came from your tooling.
- 2
Point your tool at the ingest URL
Copy the request URL from the card and append ?secret=YOUR_SECRET. In Gong and Fireflies this is a webhook setting; in Granola or any of them it can also be a Zapier or Make automation triggered when a transcript is ready.
- 3
Send whichever payload your tool produces
All three send different shapes and all three work. FeedbackFlow looks for the transcript under transcript, summary, text, notes, or data.transcript, and for an identifier under id, callId, meetingId, or transcriptId. You do not need to reshape anything.
- 4
Run a test call through it
Record a short call, let the transcript finish, and watch the item appear with the call title as its first line. If nothing arrives, check that the field carrying your transcript is one of the five recognised names, and that the secret matches exactly.
The exact Request URL and any values you need to paste are shown on the Call transcripts card inside your project settings, because they are specific to your project. Full Call transcripts setup guide.
What FeedbackFlow reads from a transcript payload
The transcript text and who hosted the call. The adapter is deliberately forgiving about field names because three vendors name them differently.
| Field | What FeedbackFlow does with it |
|---|---|
| transcript, summary, text, notes, or data.transcript | The item's text, whichever of these is present. Truncated at 8,000 characters. |
| id, callId, meetingId, or transcriptId | Deduplication key. Required: a payload with no identifier is ignored. |
| title, name, or meeting.title | Prepended to the transcript, so a topic can show which call it came from. |
| host.email | Attribution and account matching, so a transcript can be weighted by the account's value. |
What this looks like in practice
A summary arrives instead of a full transcript
Ingested. The summary field is one of the recognised names, and a summary is often the better triage input anyway.
The same call is sent twice
Recognised by identifier and discarded rather than duplicated.
A 90-minute call transcript
Truncated at 8,000 characters. Long calls are where sending the summary rather than the full transcript works better.
A payload with no transcript field we recognise
Ignored rather than stored empty. Nothing is silently half-ingested.
Limits worth knowing
What this connector does not do, so you can find out here rather than after you have wired it up.
- Transcripts are truncated at 8,000 characters, which a long call exceeds. For those, sending the tool's summary produces better topics than a truncated verbatim transcript.
- A whole transcript becomes one feedback item, so a call touching four separate problems is triaged as one thing. This is the sharpest limit of this connector.
- Speaker attribution inside the transcript is not parsed. Only the call host is captured as the requester.
- No vendor-specific signature verification, because the three differ. A shared secret in the URL is the proof of origin.
Frequently asked questions
- Should I send every sales call?
- Usually not. Most sales calls are mostly not product feedback, and every transcript is an item against your quota. Teams that get the most from this send a subset: discovery calls, churn interviews, and lost-deal debriefs, where the reasons are stated plainly. Filtering in your automation is easier than filtering afterwards.
- Why one adapter for three tools rather than three integrations?
- Because what we want from each is identical: a transcript and who was on the call. The payloads differ only in field names, so the adapter accepts several names for the same thing. Three separate integrations would be three copies of the same twelve lines, with three times the surface to break.
- A call covers several different problems. Does that work?
- Partly, and this is the honest weak point. The transcript becomes one feedback item, so triage assigns it one topic, usually the most prominent theme. Sending the tool's summary helps, and so does splitting in your automation if it can. If your calls routinely cover many topics each, this connector will under-represent the secondary ones.
- Is a secret in the URL good enough?
- It is the same approach used for Discord and the Jira webhook, for the same reason: the sender cannot sign in a way we can verify consistently, so proof of origin travels with the request. The URL is known only to you and your automation, and rotating the secret is one field in project settings. Routing through your own code lets you send it as a header instead if you prefer.
Connect Call transcripts today
Free plan. No credit card. Live in 2 minutes.