InterMIND

API & Zapier

Send meeting recaps to your CRM, help desk or spreadsheet with Zapier, or call the InterMIND API directly with a personal API key.

API & Zapier

Every recap InterMIND produces can land in the tool where you work — your CRM, help desk, task tracker or a spreadsheet — without anyone copying it by hand. Two ways in:

  • Zapier (no code): connect InterMIND once with an API key, then build Zaps on the Meeting Recap Ready trigger and the Create Meeting Link action. The same integration also works from Make, n8n or Pipedream through their generic webhook and HTTP modules, using the API below.
  • The API (for developers): a personal key, one webhook event and three endpoints.

Available on: every registered account. Guests cannot create keys. Where: Settings → API keys.

Recaps also reach any tool that has an inbound email address — add it as a recap copy recipient on the meeting or channel, no integration needed. See Recap copy.

API keys

  1. Open Settings and find the API keys card.
  2. Click Create key, give it a label (the tool that will use it, e.g. "Zapier") and copy the key. It starts with imk_ and is shown once — InterMIND stores only a hash.
  3. Revoke a key from the same card at any time. Webhook subscriptions created with that key stop immediately.

Up to 10 keys per account. Send the key as a bearer token:

Authorization: Bearer imk_…

Keys work only on the /api/v1 endpoints below; they never grant access to the web application's own API.

Zapier

  1. In Zapier, add the InterMIND app to a Zap and paste your API key when asked. The connection is labelled with your account email.
  2. Trigger Meeting Recap Ready — fires once per finished meeting you hosted, as soon as the summary exists. Fields: meeting title and link, recap link, transcript link, the summary in Markdown, summary language, start and end time, participants (name, email), host.
  3. Action Create Meeting Link — creates an ad-hoc meeting you own and returns its URL. Put it in a CRM deal, a support ticket or a calendar invite; anyone who opens the link knocks and you approve them in the room.

Typical Zaps: recap → new note on the HubSpot deal; recap → internal comment on the Zendesk ticket; recap → row in Google Sheets; new Pipedrive deal → meeting link written back to the deal.

Endpoints

Base URL: https://intermind.com/api/v1. All responses are JSON. Machine-readable contract (OpenAPI 3.1, for Make, n8n, Pipedream and AI agents): https://intermind.com/api/v1/openapi.json.

MethodPathPurpose
GET/meWho owns the key: { id, email, name }
POST/meetingsCreate an ad-hoc meeting link. Body { "title": "…" } (optional). Returns 201 { id, url, title, created_at }
GET/recaps?limit=3Your newest recaps (1–10), newest first, in the webhook payload shape
GET/webhooksYour webhook subscriptions
POST/webhooksSubscribe: { "target_url": "https://…", "event": "recap.ready" } → 201 { id, event, target_url, secret, created_at }
DELETE/webhooks/{id}Unsubscribe → 204

Limits: 10 keys and 20 webhook subscriptions per account. target_url must be https:// and publicly reachable — private network addresses are refused.

Webhook: recap.ready

Sent as POST JSON to every subscribed target_url the moment a recap for a meeting you hosted is finalised with a non-empty summary. It is sent once per meeting session. Headers:

HeaderValue
X-InterMIND-Eventrecap.ready
X-InterMIND-DeliveryUnique id of this event (<meeting id>.<session id>) — deduplicate on it
X-InterMIND-Signaturesha256=<HMAC-SHA256 of the raw body with the subscription's secret>
User-AgentInterMIND-Webhooks/1

Payload:

{
  "id": "abc-def-ghi.conf_01",
  "event": "recap.ready",
  "occurred_at": "2026-09-04T10:32:11.000Z",
  "meeting": { "id": "abc-def-ghi", "title": "Weekly sync with Acme", "url": "https://intermind.com/abc-def-ghi", "type": "adhoc" },
  "recap": {
    "url": "https://intermind.com/r/abc-def-ghi/…",
    "transcript_url": "https://intermind.com/t/abc-def-ghi/…",
    "summary_md": "## Decisions\n- …",
    "language": "en"
  },
  "session": { "started_at": "2026-09-04T10:00:03.000Z", "ended_at": "2026-09-04T10:31:40.000Z" },
  "participants": [{ "name": "Anna Müller", "email": "anna@acme.example" }],
  "host": { "name": "Anna Müller", "email": "anna@acme.example" }
}

Delivery rules: your endpoint should answer 2xx within 8 seconds. A network error, 5xx or 429 is retried once immediately. A 410 or 404 deletes the subscription. Any other failure is logged and the event is not resent — the recap email and the recap page remain the durable record. Recap and transcript links open for meeting participants who are signed in.

Telegram

Forward messages to the InterMIND bot, mirror Telegram groups into channels, and route chats into your Inbox.

Email to Channel

Give any service your channel's email address and its messages land in the channel — attachments intact, read by each member in their own language.