talat/documentation

Webhook

Webhooks let talat push every finished meeting to an HTTP endpoint of your choice. Useful for piping meetings into a self-hosted service, a Zapier / Make workflow, a Slack or Discord bot, or a custom integration. Webhooks fire once post-processing is complete, so the payload always contains the final transcript, summary, and title.

Turning webhooks on

Everything lives under Settings → Exports → Webhook:

  1. Tick Webhook.
  2. Paste your endpoint URL.
  3. Pick a method, either PUT (default) or POST.
  4. Choose a body format: Markdown or JSON (see below).
  5. Optionally add an auth header (see Authentication below).
  6. Click Test to make sure the endpoint answers.

Body format

Two body formats are supported. Pick the one that fits what your endpoint expects:

  • Markdown. The same formatted document you get from a manual export (title, summary, transcript, notes). Easiest for Markdown-aware receivers.
  • JSON. A structured object. Always present: id, title, startedAt, endedAt, durationSeconds, and participants. The notes, summary, and transcript fields are included only when those sections are enabled in the webhook config (and have content). The transcript is an array of utterances, each with speaker (the person’s name, “You” for your microphone, or null if unidentified), source (either microphone or system), and text. With Timestamps enabled, each utterance also carries startTime and endTime.

URL template variables

The URL supports a handful of template variables, substituted at send time:

  • {title}. The meeting title, URL-encoded.
  • {date}. The meeting start date (YYYY-MM-DD).
  • {id}. The meeting’s internal identifier.

So a URL like https://example.com/meetings/{date}/{id} resolves at send time into a per-meeting path.

Authentication

You can attach a single auth header to every request: a bearer token, an API key header, or any other HTTP header your endpoint requires. The value is stored in the operating system credential store (Keychain on Mac, Credential Manager on Windows), not in the settings file, and is only read when a webhook fires or when you explicitly reveal it in the settings UI.

TLS verification

TLS certificate verification is on by default. Turn it off only if you’re sending to a local or self-signed endpoint during development. Leave it on for anything hitting the public internet.

Retries

If the endpoint returns a 5xx error or the request fails to connect, talat retries up to two more times with a short delay between attempts. Three attempts total, with 2-second and 4-second backoffs. A 4xx response (bad request, unauthorised, not found) is treated as permanent and fails immediately. Fix your endpoint or settings and the next meeting will try again.

The test button

Test fires a single request to your configured URL with a small sample payload and a 5-second timeout. It uses the same method, body format, auth header, and TLS settings as a real send, so a successful test means a real meeting will reach the endpoint the same way.

Pairing with auto-export

Webhook and auto-export fire on the same post-processing event and can be used together. A common pattern is writing to a local folder for your own records and webhooking a copy to a team-wide service.