Capture a meeting through a visible Recall.ai bot.

1. An operator configures a Recall.ai API key, region, webhook secret, public Groundnote URL, and bot identity.
2. A user or administrator schedules or dispatches a bot to a meeting URL.
3. The third-party bot joins visibly under the configured name, subject to meeting-platform admission and permissions.
4. Recall.ai processes the meeting capture and sends lifecycle events to Groundnote.
5. Groundnote verifies signed webhook requests and retrieves the processed speaker-attributed transcript when available.

Groundnote sends the meeting URL, configured bot name, webhook URL, and recording configuration to Recall.ai. Recall.ai handles bot participation and capture, then returns bot status and transcript data. Provider region, platform behavior, retention, and subprocessors are governed by the customer's Recall.ai configuration and agreement.

The bot does not remove the organisation's responsibility to provide appropriate notice, obtain consent where required, follow meeting-platform rules, and limit access to authorised participants. Bot admission and visible identity should be included in the organisation's capture procedure.

• Requires a customer-provided Recall.ai account, API key, and matching regional endpoint.
• Requires a publicly reachable Groundnote webhook URL; localhost-only and fully air-gapped deployments cannot receive this workflow.
• Capture depends on the meeting platform, host settings, waiting-room admission, provider availability, and post-meeting processing.
• Transcripts are asynchronous and may not be available immediately when a call ends.

Reviewed against the Groundnote implementation on 4 September 2026. Recall.ai is a third-party provider; this page does not imply endorsement beyond technical interoperability.