Integrations

Generic webhook

When a completed report is notified, Scribe sends a JSON POST (Content-Type: application/json) to the generic webhook URL. Example request body:

{
  "event": "meeting.completed",
  "meeting": {
    "id": "meeting-id",
    "title": "Project review",
    "date": "2026-10-11T09:00:00.000Z",
    "duration_min": 30,
    "score": 7,
    "tldr": "Next steps agreed.",
    "actions": [
      "Send the proposal"
    ],
    "participants": [
      "Alex"
    ],
    "url": "https://scribeapp.eu/meetings/meeting-id"
  }
}

actions and participants are lists of strings. duration_min, score and tldr may be null. date is the meeting date, falling back to its creation date. The report link keeps Scribe’s access rules.

In Zapier, create a Webhooks / Catch Hook trigger; in Make, a Custom webhook; in n8n, a Webhook accepting POST. Copy its URL into the organisation’s notification settings, then map event and the meeting fields in your workflow. The destination server receives the data shown here. The request times out after 8 seconds; this route does not schedule retries on failure.

OneDrive / SharePoint

Report export requires a connected Microsoft account with file write permissions. It creates or replaces a Markdown file in that user’s OneDrive: Scribe/[client]/YYYY-MM-DD-title.md (without the client subfolder if no client is linked). Despite the OneDrive/SharePoint label, the current export targets OneDrive; it does not offer a SharePoint site or library selector.

Microsoft Planner

Sending actions from a completed report creates tasks with their title and a due date when valid. Scribe also attempts to add the source link and owner to the description; this does not assign the task to a Microsoft user. With a connected Microsoft account, Planner takes priority. The organisation settings define the plan and bucket; each empty field falls back to its corresponding server value. Sending is refused if either is missing. The Microsoft account must have access to the destination.

Without an available Microsoft token, sending uses the tasks webhook if configured. Its JSON differs: event is meeting.actions, meeting contains id, title, date and url, and actions contains objects with task, owner and deadline. Changes and task status are not synchronised.

MCP server

The /api/mcp endpoint accepts JSON-RPC POST requests from MCP clients with Bearer authentication (personal API key or OAuth) and read permission. Available tools are search_meetings (search), get_meeting (report, with transcript on request) and ask_meetings (questions with sources). They read accessible meetings in the organisation; they do not edit reports or create tasks.

Pre-meeting brief by email

When the scheduled job is configured on the server, it checks synchronised calendar events starting in 5 to 60 minutes. If there are other participants and past meetings or known profiles, it prepares a brief from that context and emails the calendar user in French or English according to their preference. No brief is sent without useful history. An event is marked as processed before generation: this route does not retry a failed attempt.