STACK
MENU
DOCS / THE ACCOUNT / MEETINGS

Meetings

How an agent joins the meeting room of one of its own calendar events, speaks, writes in the chat and leaves with a transcript. What the service is and what it costs is on Services.

Before you start

  • The meeting is an event on the agent's calendar that has a room. Make one with meeting: true. See Calendar.
  • The account needs credit. The first 10 minutes are held when the agent joins, and time is held 10 minutes at a time after that.
typescript
const made = await stack.calendar.createEvent('acct_123', {
  title: 'Weekly sync',
  start: '2026-11-20T10:00',
  time_zone: 'Europe/Stockholm',
  guests: ['anna@example.com'],
  meeting: true,
});

The link to the room goes out in the invite. Anyone with the link can join.

Join

prompt
Join the weekly sync as the assistant and introduce yourself.

The client calls stack_meeting_join. From code or the terminal:

typescript
const turn = await stack.meetings.join('acct_123', { event_id: made.event.id }, { passportToken });
// turn.meeting.id, turn.events
bash
npx @getstackrun/cli meeting join acct_123 cev_abc

To have the agent join by itself at the start of every occurrence, set attend: true on the event. STACK joins for it and wakes the agent with "Meeting started."

Speak and write

typescript
const next = await stack.meetings.say('acct_123', turn.meeting.id, {
  text: 'Hello, I am the assistant. I will take notes.',
}, { passportToken });
// next.events: what the others said since

await stack.meetings.chat('acct_123', turn.meeting.id, 'Notes so far: ...', { passportToken });
  • stack_meeting_say speaks the text, then waits up to wait_seconds for what the others say next and returns it.
  • stack_meeting_chat writes a line in the room's chat.
  • STACK runs no model in the meeting. The agent decides every word.
  • For a continuous stream, stack.meetings.live() opens a WebSocket on the meeting.

What a participant says, and the name they give, is content from outside. With controls on, flagged lines are withheld from the agent.

Leave

stack_meeting_leave ends the agent's part. The transcript is stored as a message of the account, and the agent is woken with "Meeting ended." A meeting also ends when everyone else leaves, when max_seconds is reached, where the join or the event sets one (there is none otherwise), or when the credit runs out. stack_get_meeting reads a meeting with its transcript.

Choose the voice

stack_set_meeting_voice sets the account's meeting voice and language. One event can have its own with meeting_voice on the event.

What counts as an action

Joining is one action. Speaking, writing, leaving and reading are free. The room and the speech are charged from credit at the provider's price, by the minute.

When it is refused

  • 409 MEETING_EVENT_HAS_NO_ROOM - the event has no room, or was cancelled.
  • 409 MEETING_ALREADY_LIVE - the agent is already in this room.
  • 409 MEETING_NOT_LIVE - the meeting has ended, or the agent is still joining.
  • 409 MEETING_ROOM_EXPIRED - the room of the event has expired.
  • 403 CONTROL_DENIED - with controls on, your policy or your own server refused it. Controls are asked as meeting.join.

Reference

Every field is on Wake-ups, Calendar and Meetings. Every tool is in the tool reference.

Meetings | Docs