Skip to main content
miniti fires a POST with the full meeting json when a meeting is saved or updated. see webhooks for the payload shape. this page collects concrete recipes you can drop in.
webhooks are unsigned and may be retried. use https and a hard-to-guess secret in the endpoint path, keep that url private, and validate incoming payloads. miniti does not support custom authentication headers.

zapier

  1. create a new zap with webhooks by zapier -> catch hook
  2. copy the zapier webhook url
  3. paste into miniti: settings → webhooks → webhook url
  4. save a meeting in miniti to send a test payload
  5. zapier will parse the json and expose all fields (including nested meeting.meddpicc, meeting.training, meeting.action_items[])
common follow-up actions:
  • gmail: send email - email yourself the summary + action items after every meeting
  • notion: create database item - one row per meeting with title, summary, action items as a checklist
  • google sheets: create row - log meetings for reporting
  • linear / jira: create issue - one issue per action item (loop over meeting.action_items)

make (integromat)

  1. new scenario -> webhooks -> custom webhook
  2. copy the webhook url into miniti settings
  3. run once, save a miniti meeting, let make learn the structure
  4. chain modules: iterator on meeting.action_items -> your task tracker, or router on event (saved vs updated)

n8n

  1. add a webhook node, method POST, path of your choice
  2. copy the production url (not the test url) into miniti
  3. downstream nodes can reference {{$json.body.meeting.summary}}, {{$json.body.meeting.meddpicc?.champion}}, etc.
example: split action items into separate rows

slack (via incoming webhook)

slack’s native incoming webhooks don’t accept miniti’s payload directly - you need a small middleman. two easy options: option 1: zapier/make - catch hook -> format a slack message -> post to channel. option 2: a tiny relay (cloudflare worker, vercel function, fly, etc.):
set SLACK_WEBHOOK_URL as a worker secret and protect the worker with a secret url path before pointing miniti at it. this small example is only the message transformation: a production relay should durably queue deliveries and deduplicate their ids. a lost response can otherwise post twice to slack.

custom endpoint (node / bun / deno)

bare-bones express receiver with a secret url path:
set WEBHOOK_SECRET on your server to a long random token. enter https://your-host/miniti/your-token in miniti. keep the full url out of access logs; the path is the credential. implement storage before using this outline.

python (flask)

filtering by mode

the payload includes meeting.training (local metrics), meeting.meddpicc (only after sales analysis has run), and meeting.questions (only after questions has run). if you only care about sales calls, check meeting.meddpicc is non-null before acting.

idempotency

use two different ids:
  • meeting.id is the record key. upsert the meeting with it so a later meeting.updated changes the same record.
  • X-Miniti-Delivery-Id identifies a delivery. remember it with the side effect or queued job so a retry does not repeat that action. X-Miniti-Attempt is informational.
do not reject every future delivery for a meeting just because you have seen its meeting.id: that would discard edits. do not assume cross-device ordering or exactly-once delivery.

changes in 3.6.0

available in macos and ios 3.6.0. its saved-meeting event waits for final processing to settle, and adds optional processing metadata. webhooks describes the fields and resend behavior.
the payload carries the transcript and available summary itself. use meeting.transcript and meeting.summary directly; a webhook is not a signal that cloud sync has finished. accept missing summaries and missing processing on older clients. in 3.6.0 a resend of the current saved meeting gets a new delivery id, while retries keep their original id and body.

see also

  • webhooks - payload shape + delivery rules