Connect Zapier and Make

Four events can start an automation: a transcript is ready (session.ready), a summary is written (summary.ready, with the summary’s key points as text), a claim gets a rating (claim.verdict, with the rating and a link to the claim), and a document is written (doc.ready). Every event carries a link back to the session.

Zapier

1. On Team, an owner or admin creates an API key (a viewer key is enough) and copies it.
2. In Zapier, choose Audicite as the trigger app, pick the event, and connect your account by pasting the key.
3. Choose Test trigger: Zapier shows your newest real event, or an example while you have none.
4. Turn the Zap on. Audicite subscribes it automatically and stops sending when you turn it off or delete it.

Revoking the API key on Team ends every Zap that uses it. The number of active Zap triggers shows on Integrations.

Make (and n8n or your own system)

1. In Make, start a scenario with Webhooks, then Custom webhook, and copy the address it gives you.
2. On Team, an owner or admin adds a webhook with that address and ticks the events you want.
3. Choose Send a test on the webhook so Make learns the shape of the data, then add the next modules.

Every webhook delivery is signed with an Audicite-Signature header (a timestamped HMAC-SHA256 of the body) that your system can check with the secret shown when you add the webhook. Failed deliveries are retried.

Tip: Deliveries carry ids, ratings, links and (for summaries) the key points. To pull a whole transcript into another app, add an HTTP step that fetches it with your API key.