Agent Control Center
Agent Control Center turns an agent into your control centre for the Google Meet and Microsoft Teams meetings of your voice agents. You connect it to an agent, choose which voice agents it may reach and, from whatever channel that agent lives on (the chat, WhatsApp, Telegram, a call), ask it how many meetings each one had, what was discussed and who attended. If a meeting is open, it tells you who is there and what is being talked about, and you can ask it to have one of your agents say something or write it in the meeting chat.
In the video, an agent follows a real Google Meet with two voice agents for you: it tells you how many meetings they have been in and what is being discussed right now, and passes them a request that one says after raising her hand and the other writes in the chat.
The node itself is the permission: an agent without it connected sees no meeting, and one with it sees only the meetings of the agents chosen on it.
When to use it
- You cannot attend a meeting and send an agent in your place: you ask on WhatsApp what is being discussed.
- During the meeting you ask it to “have Vera tell Juan the budget is approved” or “have Teo write the totals in the chat”.
- Asking “how many meetings has Vera been in this week?” or for the summary of this morning’s budget meeting.
How it works
The node is not a step of the flow: it is a tool. Connect its output to an agent’s Tools input. The agent gets a single tool, agent_control_center, and decides what to ask it:
- List meetings: how many meetings match and which, newest first. They can be narrowed by agent (by the name it joins the meeting with or by its flow’s name), by words of the subject, by date or to those open now. The number it returns is the exact total of meetings an agent got into; the times it was sent and never got in are given apart and not counted.
- Read a meeting:
- Closed: its summary, its transcript and who attended. If the meeting kept no transcript or no summary, it says so.
- Open (with Live meetings on): which agents are inside, who is attending and what has been said in the last minutes. The meeting itself is asked at that moment; nothing is stored.
- Send a task to an open meeting (with Send tasks to live meetings on): write the order in your own words, saying which agent does what, for whom, and whether it says it aloud or writes it in the chat.
You never deal with identifiers. Name the meeting by its subject and its date and time (“the budget one, this morning”); the agent finds it. If several match, it asks you which.
What happens to a task
The task goes to the meeting’s moderator, not into the conversation: nobody in the meeting hears it and it is not in the transcript.
- Aloud: the agent prepares what it will say, raises its hand and speaks when it is given the floor or when the room goes quiet. It never interrupts.
- In the chat: the agent writes the message. If you give it the exact text, it writes it as it is and the tool confirms the chat took it.
- The agent you name is the one that does it. If you name none, the moderator picks the one that fits best.
- How each agent was invited is respected. One sent to listen only, or that only answers when asked, does not speak up on its own; one without the chat does not write. In those cases the task is refused and you are told why.
The answer comes when the moderator decides who takes the task, not when it is done. To see how it went, ask about the meeting again: you will see each task with where it stands (preparing, hand raised, said, written in the chat or failed).
Configuration
| Field | What it does |
|---|---|
| Agents | The voice agents this node may reach, picked from the list of your flows with a Voice Agent. Empty: none. |
| Live meetings | Allows looking inside an open meeting: who is attending and what is being said. Off: an open meeting only shows when it started and which agents were sent. |
| Send tasks to live meetings | Allows handing tasks to an open meeting. Needs Live meetings. |
The other fields (Action, Agent, Subject, Since, Until, Open only, Meeting, Task, Recent minutes) are filled in by the agent when it uses the tool. You do not need to touch them.
It is enough for the node to reach one of a meeting’s agents to see that meeting and send it tasks, also for another agent in it: the moderator is shared by all of them.
What it returns
- When listing:
count(meetings an agent got into),not_entered(times it was sent and never got in, not counted) androws, one row per meeting withmeeting_id,subject,platform,started_at,ended_at,duration_minutes,open(whether it is still going),stateandagents.statesays where it stands:open,closed,starting(the agents have not joined yet) orclosing(it has just ended and its summary is being written). - When reading a closed meeting: the above plus
summary,transcript(Name: textper line),transcript_lines,attendeesandnot_kept, which says what the meeting did not keep. A long transcript is read in parts withnext_offset. - When reading an open meeting: the row plus
agents(each agent and whether it is inside yet),attendees,people_count,hands_up, thetranscriptof the last minutes,earlier_summaryandowner_tasks(your tasks and where each stands). - When sending a task:
agent(who took it),how(voiceorchat),statusandmessage. If it is refused, the reason.
Keep in mind
- Meetings are kept for 7 days.
- The subject is the purpose given when the agents were invited, not the calendar’s title. A meeting invited without a purpose is told apart by its date, its time and its agents.
- The attendees of a past meeting are known only if it kept its transcript.
- Dates and times are given in UTC.
- An agent taken out of a meeting while it is still waiting to be let in counts as having attended. One the meeting turns away, or that nobody lets in, does not.
- A meeting that has just ended takes a minute or two to have its summary. Until then it shows as
closing. - What the agent tells you about a meeting is stored in that agent’s conversation, like any other answer of its own, also when the meeting is set not to keep its transcript.
- A node saved before an update keeps its fields: update the node to see the new ones.
Security
Whoever can talk to the agent that carries this node can ask about the meetings of the chosen agents and, with tasks on, make them speak or write in a meeting. Connect it only to agents you use yourself. If other people need the same agent, make a copy without the node.
Related components
- Join Meeting: send agents to a meeting from a flow.
- Meeting History: read the meetings in a flow with no agent.
- Voice Agent.
- Agents in meetings: invite your agents to a meeting and follow it live from the dashboard.