Aprende mokapen

Jamie

The Jamie integration brings meeting transcripts and AI notes from meetjamie.ai into Mokapen automatically. When a meeting is processed in Jamie, Mokapen can create a document, a note, or keep only a lightweight pointer, and — when possible — link the result to the matching appointment already on your calendar.

Jamie is a privacy-first AI note taker that works without a meeting bot. This integration is for sales and customer success teams who already record with Jamie and want the outcome (summary, action items, full dialogue) next to the CRM appointment.

General integrations overview: Integrations.

Requirements

• A Mokapen plan that includes the Jamie integration (Premium — medal icon on the page if not available on your plan).
• A Jamie account on Pro / Team / Enterprise (or eligible) plan with permission to create API keys and webhooks.
• Optional but recommended: Google Calendar or Outlook Calendar synced with Mokapen, so appointments can be matched by calendar event id.

Connecting

Jamie connects with an API key (no OAuth). You paste the key once in Mokapen, then configure the webhook that notifies Mokapen when a meeting is ready.

1. User menu → Integrations → Jamie.
2. Click Sync / Connect (requires an adequate Premium plan).
3. Create an API key in Jamie: Settings → Developers → API Keys (developer docs). Use a personal (/v1/me) or workspace (/v1/workspace) key.
4. Paste the key in Mokapen and confirm Connect.
5. When the link succeeds, the page shows the connection and unlocks webhook and save settings.

Webhook

After connecting the API key, the Integrations → Jamie page shows a webhook URL to copy. In Jamie go to Settings → Integrations → Webhooks, create a webhook, paste the Mokapen URL, and subscribe to meeting.completed.

Choose authentication in Jamie:

• API key (recommended) — Jamie sends the secret in x-jamie-api-key (or a custom header). Paste the same secret in Mokapen Webhook secret.
• Signature — Jamie signs with HMAC-SHA256 in x-jamie-signature. Paste the signing secret in Mokapen.

Press Save on the Mokapen page after changing webhook secret or save options.

Save settings

Still on Integrations → Jamie, choose how each processed meeting is stored in Mokapen:

• Document — creates a document with the meeting content (best for long transcripts).
• Note — creates a note linked to the matched appointment when possible.
• URL — stores a lightweight pointer without importing the full text body.

You can also toggle whether to include the summary (and action items) and the transcript.

Matching appointments

When a transcript arrives, Mokapen tries to attach it to an existing appointment using the calendar event externalId from Jamie (Google Calendar or Outlook Calendar sync ids already stored in Mokapen).

If no appointment matches, the document or note is still created — it is simply not linked to a calendar event.

Sharing with teammates

Like other Mokapen integrations, you can share the Jamie connection with selected teammates or the whole organization from the sync sharing controls on the settings page.

What happens after a meeting

1. Jamie finishes processing and fires meeting.completed (payload includes summary, transcript and tasks).
2. Mokapen receives the payload, optionally verifies the API key or HMAC signature, and queues a background job.
3. The job uses the webhook content (and can fall back to the Jamie API meetings.get when needed), applies your save options, and creates the document/note.
4. If an appointment match is found, the new item is linked to that appointment.
5. Duplicate deliveries for the same meeting are ignored via sync deduplication.

Common issues

• Nothing appears after a call — check that the webhook URL is correctly pasted in Jamie, that the event is meeting.completed, that the integration is still connected, and that the Premium plan includes this app. Also ensure the queue worker is running.
• Document created but not on the appointment — the calendar externalId did not match. Keep calendar sync active for the most reliable match.
• Webhook rejected / signature errors — the secret in Mokapen must match exactly what Jamie shows when creating the webhook; regenerate both sides if unsure.
• Only a short record is saved — check Save as and the summary/transcript checkboxes; URL mode intentionally skips the full body.
• API key invalid — regenerate the key in Jamie (Settings → Developers → API Keys) and reconnect. API access requires an eligible Jamie plan.

Disconnecting

Use Disconnect on the Integrations → Jamie page (available to the user who connected the integration). Remove or disable the webhook in Jamie as well if you no longer want deliveries.

Documents and notes already created stay in Mokapen; disconnecting only stops new transcripts from arriving.

Frequently asked questions

Q: Does Mokapen join the meeting as a bot?

A: No. Jamie records without a bot; Mokapen only receives the processed notes via webhook/API.

Q: Personal or workspace API key?

A: Both work. Mokapen detects the scope during connect. Use a workspace key if you need meetings across the whole Jamie workspace.

Q: Where is the official Jamie documentation?

A: API and Webhooks.