Ръководството на Мокапен

Read.ai

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

This is designed for sales and customer success teams who already record calls in Read.ai and want the outcome (summary, action items, full dialogue) available next to the CRM appointment, without exporting files by hand.

General integrations overview: Integrations.

Requirements

• A Mokapen plan that includes the Read.ai integration (Premium — medal icon on the page if not available on your plan).
• An active Read.ai account with permission to add webhooks in Integrations.
• Optional but recommended: Google Calendar or Outlook Calendar synced with Mokapen, so appointments can be matched by calendar event id or meeting URL.

Connecting

Read.ai does not use a simple API-key login in Mokapen. You activate the integration first, then paste the Mokapen webhook URL into Read.ai so meeting reports are delivered when they are ready.

1. User menu → Integrations → Read.ai.
2. Click Sync / Connect to activate the integration in Mokapen (requires Premium).
3. Copy the webhook URL shown on the settings page.
4. In Read.ai → Integrations, create a webhook for the meeting_end event and paste that URL.
5. Optional: copy the signing key from Read.ai into the Webhook secret field in Mokapen, then save.

Webhook

The webhook URL on the Integrations → Read.ai page is the endpoint Read.ai must call. Paste it in Read.ai Integrations settings for the meeting_end event. If Read.ai shows a signing key, paste it into Webhook secret in Mokapen so requests can be verified via X-Read-Signature.

Save settings

Still on Integrations → Read.ai, choose how each processed meeting is stored in Mokapen:

• Document — creates a document with the meeting content (best for sharing long transcripts with the team).
• Note — creates a note linked to the matched appointment or available in your notes stream.
• URL — stores mainly the link back to the recording in Read.ai, without importing the full text body.

You can also toggle whether to include the summary and the transcript (AI summary, action items and full transcript). Turning both off with URL mode keeps only a lightweight pointer to the external recording.

Matching appointments

When a transcript arrives, Mokapen tries to attach it to an existing appointment:

1. First it looks for a calendar sync id already stored for that meeting (Google Calendar or Outlook Calendar integrations).
2. If that fails, it compares the meeting URL from Read.ai with the URL field on appointments.
3. If no appointment matches, the document or note is still created — it is simply not linked to a calendar event.

Tip: keep the same meeting link on the appointment card that Read.ai records (Zoom, Meet, Teams…), and keep calendar sync active for the most reliable match.

Sharing with teammates

Like other Mokapen integrations, you can share the Read.ai connection with selected teammates or teams from the sync sharing controls on the settings page. Shared users can benefit from transcripts landing in the organization without each person connecting their own key.

What happens after a meeting

1. Read.ai finishes processing the recording and fires the webhook (or Grain delivers meeting_end).
2. Mokapen receives the payload, optionally verifies the signature/secret, and queues a background job.
3. The job fetches summary/transcript details via API when needed, applies your save options, and creates the document/note/URL record.
4. If an appointment match is found, the new item is linked to that appointment so it appears in context.
5. Duplicate deliveries for the same recording are ignored via sync deduplication, so retries do not create double documents.

Common issues

• Nothing appears after a call — check that the webhook is correctly pasted in Read.ai (except Grain, where it is automatic), that the integration is still connected, and that the Premium plan includes this app.
• Document created but not on the appointment — the meeting URL or calendar event id did not match. Open the appointment, confirm the URL, and ensure calendar sync is active.
• Webhook rejected / signature errors — the secret in Mokapen must match exactly what is configured in Read.ai; regenerate both sides if unsure.
• Only the link is saved — check Save as and the summary/transcript checkboxes; URL mode intentionally skips the full body.
• API key invalid — regenerate the key in Read.ai and reconnect from Integrations → Read.ai.

Disconnecting

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

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

Use cases

• Sales call follow-up — after a discovery call recorded in Read.ai, the summary lands as a document on the appointment: the AE can share action items without rewriting notes.
• CS QBR archive — quarterly business reviews stay searchable in Mokapen documents, linked to the customer appointment.
• Handoff between roles — SDRs record demos in Read.ai; closers open the matched appointment and read the transcript without switching tools.
• Lightweight CRM pointer — use URL save mode when you only need a deep link back to Read.ai from the appointment card.

Frequently asked questions

Q: Does Mokapen record the meeting itself?

A: No. Recording and transcription happen in Read.ai. Mokapen only receives the result via webhook and stores it according to your settings.

Q: Is an API key always required?

A: No API key in Mokapen for Read.ai: activate the integration and configure the webhook in Read.ai.

Q: What if there is no matching appointment?

A: The document or note is still created. You can link it manually later, or fix the meeting URL / calendar sync for future calls.

Q: Can teammates use my connection?

A: Yes, if you share the integration with them from the sync sharing settings on the Integrations page.

Q: Will reconnecting duplicate old meetings?

A: Mokapen deduplicates by sync identity for recordings already imported. New meetings continue to create new documents/notes.

Q: Where do I find the settings later?

A: User menu → Integrations → Read.ai. Webhook URL, secrets and save options are on that page after connecting.