Skip to main content
Recall.ai meeting agents join any Google Meet, Zoom or Teams call. The meeting agent hears the meeting, and it can speak and show video from a web page you host. A Trigger.dev chat.agent works well behind it: one session follows the whole meeting, sees every sentence, and only runs the model when it has something to say. This guide shows the key parts.

What you need

  • A Trigger.dev project
  • A Recall.ai account: an API key, your region, and a workspace secret for signing webhooks
  • An API key for your model (the example uses the Vercel AI Gateway for the model and the voice)
  • A public place to host a web page, like Vercel

How it fits together

Meet or Zoom connects to the Recall.ai meeting agent. The meeting agent sends each sentence to the Trigger.dev agent as a webhook. The Trigger.dev agent's answers go to a web page, which Recall.ai loads as the meeting agent's video feed. The page sends the meeting agent's voice and a screenshare back into the call.
  1. Recall.ai puts a meeting agent in the call and sends each finished sentence to a Trigger.dev webhook.
  2. Every sentence goes into the same agent session, which decides whether to answer.
  3. The meeting agent’s video feed is a web page. It follows the agent session, speaks the answers and starts a screenshare.

1. Receive the transcript as a webhook

Define a hosted endpoint for Recall.ai. It verifies each request with your workspace secret:
src/trigger/endpoints.ts
Run npx trigger.dev@latest dev, then set the secret from the Recall.ai dashboard’s API keys page:
You don’t add the endpoint URL in Recall.ai’s dashboard. You pass it when you create the meeting agent, as a real-time endpoint (step 5).

2. Route every sentence into one session

The key decides which agent session a webhook goes to. Same key, same session. Give the transcript a constant key, so every sentence of the meeting lands in one conversation:
src/trigger/agent.ts
A constant key handles one meeting at a time. To run several calls at once, put the meeting agent’s ID in the key. The same key also lets other webhooks join the conversation. Give a Resend inbox endpoint the same key, and the agent sees new emails next to the meeting.

3. Decide when to answer

Each sentence runs the agent’s onAction, which is plain code. To reply, return chat.turn(). To stay quiet, return nothing, and the model doesn’t run. Simplified from the example:
src/trigger/agent.ts
Transcript events keep the run busy for the whole meeting, so set maxDuration on the agent to cover a long call. Pass the transcript to the model on each turn, so it knows what’s being said:
src/trigger/agent.ts
Everything the agent writes is spoken aloud, so keep its system prompt plain and short. In the example, it replies SILENT when a sentence wasn’t meant for it, and the page skips those.

4. Give the agent video and audio (and screen sharing)

Recall.ai can use a web page as the meeting agent’s video feed. Whatever the page shows is the meeting agent’s video, and whatever audio it plays is its voice. The page URL carries a read-only watch token for the session:
src/trigger/services.ts
The page follows the agent’s output with a TriggerChatTransport in watch mode, the same way a chat app shows a reply:
web/app/page.tsx
When an answer finishes, the page:
  1. Turns it into speech in a server route, so your model key stays on the server. The example uses Gemini TTS through the AI Gateway.
  2. Waits until the meeting audio has been quiet for 1.2 seconds. Recall.ai feeds the meeting audio into the page through getUserMedia().
  3. Plays the voice. If the turn has something to show, it also asks Recall.ai’s output_media API, from a server route, to screenshare a second view of the same page.
The page has to be public, so Recall.ai can load it, and its routes spend your credits. On Vercel, turn on Deployment Protection, create a Protection Bypass for Automation secret, and add it to the URL you give Recall.ai.

5. Send the meeting agent to a call

Create the meeting agent with the transcript going to your recall endpoint and the page as its video feed (real code, with a few fields cut):
src/trigger/join-meeting.ts
Then tell the Trigger.dev agent which meeting agent it’s speaking through, with an action:
src/trigger/join-meeting.ts
Trigger join-meeting from the Test page with a meeting link, admit the meeting agent, and talk to it by name.

Next steps

  • Recall.ai webhooks: verification and real-time events
  • Session routing: route webhook events into an agent’s session
  • Actions: onAction and chat.turn()
  • Watch tokens: follow a session from another page
  • To deploy, run npx trigger.dev@latest deploy and set the same variables and secrets with --env prod