The webhook connector is the general-purpose exit from Fivo. When a report is shared to it, Fivo posts the whole report as JSON to a URL you own, so you can feed any system that is not in the integrations list.
What it adds to your Brain
Nothing comes back from a webhook: it is outbound only, and it does not feed your graph. What it gives you is the full report, as data, wherever you need it.
Each delivery is an HTTPS POST with a JSON body containing the report: its id, title, date, source (meeting, audio or document), participant names and their speaking time for meetings, language, the summary, the chapters with their timestamps and descriptions, the task list with title, status, assignee and priority, and everything that was said in the meeting as a list of chunks with speaker and timestamp.
Typical uses: push reports into a data warehouse, trigger an automation platform, or post summaries into an internal tool.
Before you start
- An HTTPS endpoint that accepts POST requests with a JSON body and answers with a success status. Plain HTTP is not accepted.
- Optionally, a secret header your server will check, so it can tell Fivo's requests from anyone else's. The webhook feature is available on paid plans.
Step by step
- Open Integrations in app.fivo.ai and find Webhook.
- Click Connect. No sign-in or API key is needed; Fivo asks you for the connection details instead.
- Fill in:
- Destination URL: the full address that starts with
https://where reports will be sent. - Custom header (optional): one header in the form
Name: value, for exampleX-Fivo-Token: your-secret. It is sent with every delivery to this URL. Headers that describe the request itself (Host, Content-Type, Content-Length, Transfer-Encoding, Connection) are not allowed.
- Destination URL: the full address that starts with
- Click Continue. Fivo saves the details and never shows the secret values again.
- From a meeting report, share it to the webhook. Fivo posts the report to your URL.
What happens next
Fivo sends one POST per shared report and only looks at the status of your answer: a success status means delivered; anything else is treated as a failure. The body of your response is never read, so you can answer with an empty 200.
The custom header is tied to the URL you saved it with. If a delivery is ever directed to a different URL, the saved header does not travel with it.
Who can share a report to the webhook follows the report's own permissions in Fivo: you can send what you can open. See Meeting reports and Permissions: what your Brain can see.
Disconnect
Open Integrations, select Webhook and click Disconnect. Fivo forgets the URL and the header, and no further reports are sent.
Troubleshooting
- "Enter a full address that starts with https://". Only HTTPS URLs are accepted. Include the scheme and the full host.
- "This doesn't have the expected format." The custom header must be exactly
Name: valueon one line, with a valid header name and no reserved header. Only one header is accepted. - Deliveries fail. Your endpoint must answer with a success status within a reasonable time. Check its logs for the POST, and make sure it does not require authentication Fivo does not send.
- Nothing arrives. The webhook sends only when a report is shared to it. Share a report from its page and watch your endpoint.
Related: Connect your tools.
- integration
- workflow