Meeting Ended Trigger

Overview

The Meeting Ended trigger starts a workflow when a notetaker bot dispatched by a Meeting Notetaker action finishes. By default it fires on the done status — when the recording is processed and the transcript is ready — and delivers the full speaker-labeled transcript to the workflow, so downstream nodes can summarize, log, and route it without an extra fetch.

Configuration

• Credential (optional) — scope the trigger to bots dispatched with one Recall.ai credential, or leave blank to fire for any credential in the workspace
• Fire On — bot statuses that fire the trigger: done (transcript ready), call_ended, or fatal (bot failed). Nothing selected means done only
• Meeting URL Contains (optional) — only fire for meeting URLs containing this text (e.g. meet.google.com)

Output variables

• {{$json.botId}}, {{$json.status}}, {{$json.meetingUrl}}
• {{$json.transcript}} — speaker-labeled segments with timestamps
• {{$json.transcriptText}} — plain text ("Speaker: line" per row), ready for an AI Prompt node
• {{$json.participants}} — meeting participants
• {{$json.metadata}} — whatever the Send Bot action attached

Webhook setup

Events reach Falcon Builder through a Recall.ai webhook endpoint pointed at /api/webhooks/recall/bot-status, verified with the Svix signing secret stored on your Recall.ai credential. Only bots dispatched by your own workflows fire triggers — events for unknown bots are ignored.

Required Credentials