Join Meeting
Join Meeting sends one or several of your voice agents to a Google Meet, as the Invite to a meeting button of the Voice Agent console does, but from a flow. When the meeting ends, the flow carries on with the summary and the transcript, ready to be emailed, stored or turned into pending tasks.
When to use it
- An agent attends the project meeting every Monday: a scheduled flow sends it and, at the end, emails the minutes to the attendees.
- Sending an expert (code, product, support) to a meeting when someone asks for it in a chat.
- Collecting what was said in a meeting to take it to a CRM or a task manager.
Configuration
| Field | What it does |
|---|---|
| Meeting link (required) | The Google Meet link (https://meet.google.com/abc-defg-hij). |
| Voice Agents (required) | One to four of your voice agents, picked from the list (your flows with a Voice Agent; the list loads when the node opens). Four at most. Each joins with its deployed version. |
| Agent joins Google Meet as | One field per chosen agent: who that agent is in Google Meet. The agent’s own setting (default): the Google account chosen for that agent when inviting from the dashboard, or a guest if it has none. Guest (the agent’s name): it asks to join under its own name. Or one of your Google accounts for meetings: it joins as that user, under that account’s name. The last option, Sign in with a Google account…, opens Google’s sign-in to add an account from the node itself (also possible under Voice Agent → Meetings → Settings). Several agents can use the same one. Not used in Microsoft Teams. |
| Participation | Participate: they answer when spoken to and raise their hand to add something. Answer only when asked. Listen only: they never speak. |
| Keep | What the meeting keeps and this step returns: Summary and transcript (default), Summary or Nothing. |
| Summary prompt | How the summary is written when the meeting ends. It comes filled with NappAI’s (a short summary, the decisions and the action items with their owner, in plain text); change it to ask for other sections (goals, risks, next steps), a format (bullets, a table, your minutes template) or a focus. The transcript does not change: it is always word for word. The meeting’s language is added on its own. Empty: NappAI’s. Hidden with Keep = Nothing. |
| Moderator context (tokens) (advanced) | How much the model that follows the meeting reads at once. 0 (default): the account’s meetings setting (128000 unless changed). Never more than the model takes. The summary, the artifact and the questions about the meeting are written within it; a longer meeting is summarised part by part. The agents’ models are not affected. |
| Create artifact | Off by default: on, when the meeting ends a detailed web page of everything said is written (summary, decisions, tasks, topics and screens), kept under Artifacts of whoever runs the flow. The meeting then keeps everything that is said, whatever Keep says. See Meeting artifacts. |
| Purpose of the meeting | Optional: what the meeting is for. The moderator uses it to decide when the agents can help. |
| Use the meeting chat (advanced) | On by default: the agents read the meeting’s chat (people can write to them there) and write in it what is better read than heard: links, figures, lists. |
| See shared screens (advanced) | Off by default: on, the agents can look at a screen someone shares in the meeting when asked about it. What is shared may be private. |
| Language (advanced) | The language spoken in the meeting, as a code: es, en, fr, pt-BR… The agents listen, speak and write the summary in it, and the Meet captions they use to tell who is speaking are set to it. Empty: Spanish. |
| Words to stop an agent and Seconds to stop an agent (advanced) | How much someone must say over an agent that is speaking to make it stop and listen: this many words, for this long. 4 words over 1.2 seconds by default. Lower stops it sooner; higher, a “yes” or a cough never cuts it. |
| Wait for the meeting to end | On (default): the flow continues when the meeting ends. Off: it continues as soon as the agents are sent. |
| Longest wait (minutes) | If the meeting is still going after this, the step returns what there is and the agents stay. 120 by default. |
While the meeting lasts, in a production run (API, webhook or schedule) the run pauses at this step and the same run continues when it ends. No worker is held for the hour the meeting may last. What must happen afterwards (email the minutes, store them) goes connected after this node.
Output
The Meeting output returns plain fields, read at a glance and used as they are in the next steps ({summary}, {transcript}):
| Field | What it is |
|---|---|
meeting_id, meeting_url | The meeting. |
status and status_text | ended, sent (sent, without waiting), failed (no agent could join), timeout (still going after the longest wait) or in_meeting. |
agents | The agents and their status in one line: Vera · Cliente (left), Teo · Código (left). One that could not join, with the reason. |
agent_count | How many agents were sent. |
goal | The purpose given to the meeting. |
started_at, ended_at | Start and end (2026-11-09 16:41 UTC). |
duration_minutes | How long it lasted. |
summary | The summary written by the meeting’s moderator. |
transcript | The transcript as text, one line per turn (Name: text). |
transcript_lines | How many turns it has. |
When it runs, the node also shows the meeting at a glance: status, agents, duration and the start of the summary.
Example
The weekly meeting’s minutes, sent by themselves:
- Schedule a flow on Mondays at 9:55 with Join Meeting, the meeting link and the project’s agent.
- Connect its output to a model that extracts the pending tasks and who owns them from the summary and transcript.
- Send the result with Gmail Message.
Related components
- Meeting History: meetings that already ended, with their summary and transcript.
- Outbound Call: the agent makes a phone call.
- Voice Agent.