Meeting Agent (Zoom)

Who is this for? This article has two parts. For Users covers how to use the meeting agent in your Zoom calls. For Admins covers how to set Adomo up in Zoom and control what the agent is allowed to do.

The Adomo meeting agent joins your Zoom meetings as a quiet participant, listens for a wake word, and responds when spoken to. It can pull a report, look up a customer, draft a follow-up, or kick off a process on the spot, on behalf of whoever asked.

The agent acts as a real teammate: it only does what the person asking is authorized to do, every action is logged, and anything that would need sign-off under your DOAG policy is declined in the meeting rather than run without approval.

For Users

What you can ask the agent to do

Anything Adomo can do for you outside the meeting, phrased in plain English. For example:

"Adomo, what was last quarter's pipeline coverage for the West region?"
"Adomo, pull up the renewal process for Acme and tell me where it stands."
"Adomo, draft a follow-up email to the customer summarizing what we just agreed."
"Adomo, kick off the vendor onboarding SOP for the company we just discussed."

The agent replies in the meeting as text shown in the Adomo in-meeting panel. Actions that would require sign-off under your DOAG policy are not executed in the meeting - the agent declines and explains that the action needs approval, and the denial is logged on the session. Run the action from the Adomo app afterward to go through the normal approval flow.

When the agent is (and isn't) listening

The agent only acts when it hears a wake word your admin has configured (by default "Adomo", "Hey Adomo", or "Hi Adomo" - matching is fuzzy, with a sensitivity threshold your admin can tune). Until then, nothing is processed by the LLM. Speech is transcribed live by Zoom's own real-time media service, and the agent receives only the lines it needs to respond to.

You'll see a visible indicator in the Adomo in-meeting panel whenever the agent is listening for a wake word, and a second indicator when it's actively processing a request. Session records (wake-word hits, agent responses, tool calls, and denials) are kept on the meeting session and visible to admins under Meetings > Sessions.

Link your Zoom account (one-time)

So the agent can act "as you" during meetings, you link your Adomo account to your Zoom identity once:

In Adomo, open Integrations > Zoom.
Click Link Zoom Account.
Sign in to Zoom and approve the permissions.
You'll be returned to Adomo with a Linked status showing which Zoom account you linked.

You can check your status (Linked / Expired / Error) and unlink at any time from the same page.

If you don't link your Zoom account, the agent still listens in meetings you're in, but will treat you as an external participant: it will answer general questions but won't use tools or take actions on your behalf.

Unlink your Zoom account (revoke access)

You can revoke the meeting agent's access to your Zoom identity at any time:

In Adomo, open Integrations > Zoom and click Unlink. This deletes the stored Zoom token immediately and stops the agent from acting on your behalf; your status returns to unlinked.
To also remove Adomo's access on Zoom's side, sign in at marketplace.zoom.us, open Manage > Added Apps, find the Adomo app, and click Remove. We recommend doing both.

After you unlink, the agent treats you as an external participant in meetings: it will answer general questions but won't use tools or take actions on your behalf until you link again.

Join a meeting with the agent

If your workspace has installed the Adomo Zoom app, the agent is already available in your meetings. It joins automatically when real-time media starts for a meeting covered by the Adomo Zoom app - there is no separate invite step. You can pause it at any time with the Pause button in the Adomo panel.

During the meeting you can open the Adomo panel in Zoom to see:

Whether the agent is connected
Actions the agent is running or has completed, with their results
The agent's responses
A chat box for messaging the agent directly

What the agent will not do

Take actions beyond your own permissions. If you can't do it in the Adomo app, the agent can't do it for you in the meeting either.
Act on behalf of someone who hasn't linked their Zoom account. External participants get general answers only, no tool use.
Bypass approvals. Anything that requires a human sign-off outside the meeting is not executed in the meeting: the agent declines, and you run the action from the Adomo app afterward.
Auto-escalate. If a request needs admin or builder permissions you don't have, the agent tells you that in plain language rather than trying anyway.

User FAQ

Can I mute the meeting agent?

Yes. The agent only acts on wake-word hits, so simply not using the wake word is the easiest "mute". You can also disable the Adomo app for a specific meeting from the Zoom apps panel.

What if two people say the wake word at once?

Requests are handled one at a time in the order they were spoken; a second request is queued and answered after the first finishes. The session log shows which participant each response was for.

Can I review what the agent did?

Session review is an admin feature. Ask a workspace admin to open Meetings > Sessions, where every wake-word hit, agent response, tool call, and denial for your meeting is logged.

For Admins

Setting up the meeting agent has four pieces:

Create a Zoom Marketplace app and connect it to Adomo.
Configure what the meeting agent is allowed to do.
Have users link their Zoom identities.
(Optional) Review meeting sessions in the admin panel.

1. Create a Zoom Marketplace app

Before you start, you need:

A Zoom account with Real-time Media Streams (RTMS) available and enabled in your Zoom account settings.
A Zoom user with Marketplace developer rights.
Workspace admin rights in Adomo.
Go to marketplace.zoom.us and sign in with a Zoom account that can create apps for your organization.
Click Develop > Build App and choose the General App type.
Set the app's Redirect URL to the OAuth Callback URI shown on the Zoom integration's Configure form in Adomo (open Integrations > Workspace, find Zoom, and choose Configure). Set the Webhook Endpoint URL to the webhook URL shown in Meetings > Agent Config after you set the Zoom App Name (see step 2 below). Copy both exactly - they're specific to your workspace.
Under Scopes, add the scopes needed for the meeting agent:
- user:read:user and user:read:email - identify the user who installs the app
- The RTMS scopes Zoom requires for real-time media access
- Any additional scopes for tools you plan to expose (for example, cloud recording read if you want the agent to reference past meetings)
Under Event Subscriptions, subscribe to the RTMS meeting events: meeting.rtms_started, meeting.rtms_stopped, and meeting.rtms_interrupted.
In the Zoom app's App Credentials section, copy:
- Client ID
- Client Secret
- Secret Token (Adomo calls this the Webhook Secret Token)
In Adomo, paste each value into the matching field on the Zoom integration's Configure form, then save. Adomo verifies the configuration and reports success or a specific error.
Publish or distribute the app according to your org's Zoom policy. Most customers use an internal ("intra-account") app so only people in your Zoom account see it.

If credentials later expire or get revoked, the connection will show as Expired or Error on the Zoom integration page with a link to re-authenticate.

If sessions show the agent never receiving audio, confirm RTMS is enabled for your Zoom account and the RTMS event subscriptions were added in step 5.

2. Configure the meeting agent

Open Meetings > Agent Config and set:

Zoom App Name - a URL slug that must match your Zoom Marketplace app. Adomo shows the resulting webhook URL to paste into Zoom.
Status - the Enabled / Disabled toggle for the workspace. You must save the configuration before you can enable it. Disabled means no new agent sessions start, even if the Zoom app is installed.
Model - the LLM model name the agent uses (free text, for example claude-sonnet-4-6).
System prompt - the base instructions for the agent (tone, guardrails, what to decline). A sensible default is prefilled.
Wake words - one or more trigger phrases (by default "Adomo", "Hey Adomo", and "Hi Adomo"), plus a similarity threshold controlling how close a spoken match must be.
Tool Access - which workspace tools the agent may invoke during meetings. Participants' own permissions and your DOAG policy still apply. If a tool isn't checked here, the agent cannot call it during a meeting, even if a user has access to it in the app.

If you haven't configured the meeting agent, users can't start sessions. There is no implicit default set - this is intentional, so nothing runs in live meetings without admin consent.

Enabling or disabling the agent takes effect on the next meeting start. Meetings already in progress continue until they end.

3. User identity linking

For the agent to act on behalf of a specific participant, that participant must have linked their Adomo account to their Zoom identity.

Users do this themselves from Integrations > Zoom: click Link Zoom Account, sign in to Zoom, and approve the permissions.
Each user manages their own link from that page, where they can see their status (Linked / Expired / Error) and unlink at any time. There is currently no admin roster of link status.
If a user's link shows Expired, have them re-link from the same page; the old token is replaced. Until then, the agent treats them as an unlinked external participant.

What happens to participants who aren't linked. The agent treats them as unauthenticated external participants: they can ask general questions and get LLM-only answers, but the agent will not call tools or take actions on their behalf. This is the conservative default and cannot be loosened.

4. Review meeting sessions

Meetings > Sessions shows every meeting the agent has joined, with:

Zoom meeting UUID, status, start and end times, and duration
Counts of transcript lines, wake-word hits, tool invocations, and policy denials, plus a timeline of each wake-word hit (participant and matched word), agent response, tool invocation, denial, and error
Errors or reconnection events (for example, if the RTMS stream dropped mid-meeting)

Use this panel to audit the agent's behavior and debug failed sessions.

Revoke the Zoom integration

To remove Adomo's access to Zoom for the whole workspace:

Stop new sessions. In Meetings > Agent Config, switch Status to Disabled. No new agent sessions will start; meetings already in progress finish normally.
Clear the connection in Adomo. Open Integrations > Workspace > Zoom > Configure and remove the stored credentials (Client ID, Client Secret, and Webhook Secret Token), then save. Adomo stops making Zoom API calls and the connection shows as not configured.
Uninstall the app on Zoom's side. Sign in at marketplace.zoom.us with a Zoom admin or the developer account that owns the app, open Manage > Added Apps, and Remove the Adomo app. This deauthorizes Adomo and revokes the OAuth tokens Zoom issued. If you no longer need the app at all, delete or deactivate the Marketplace app itself as well.

Individual users can revoke their own link without affecting the rest of the workspace by unlinking from Integrations > Zoom (see Unlink your Zoom account under For Users).

What happens to data. Unlinking or clearing the configuration removes the stored Zoom tokens right away. Session records already captured (wake-word hits, agent responses, tool calls, and denials) remain under Meetings > Sessions for your workspace's audit-log window; contact your account team to delete them sooner or about specific retention requirements.

Security model (what the agent can and can't do)

Per-user scoping. When the agent invokes a tool during a meeting, it uses the requesting participant's identity and credentials, not a shared service account. If the participant can't do something in the Adomo app, they can't do it via the agent either.
No privilege escalation. If a request requires admin or builder permissions the participant doesn't have, the agent declines in plain language and logs the denial in the audit trail.
No ambient authority for external participants. Anyone without a linked Adomo identity gets LLM-only answers.
Approvals are not bypassed. Actions that would require sign-off under your DOAG policy are not executed in the meeting - the agent declines, explains that the action needs approval, and the denial is logged on the session. The participant can run the action from the Adomo app afterward to go through the normal approval flow.
Everything is logged. Every wake-word hit (who triggered it and which word matched), every response the agent gave, every tool call, and every denial is recorded on the meeting session and available in the admin panel.

Admin FAQ

Can I limit the agent to certain meetings?

Yes. The Adomo Zoom app is installed per user / per meeting in the standard Zoom Marketplace way. Combine that with the Tool Access list to control both where the agent runs and what it can do when it does.

Can I disable the meeting agent for the whole workspace temporarily?

Yes. Switch the Status toggle to Disabled in Meetings > Agent Config. Active meetings continue until they end; no new meetings will use the agent.

How do I rotate Zoom app credentials?

Update them in the Zoom Marketplace, then paste the new values into the Zoom integration's Configure form (Integrations > Workspace > Zoom > Configure) and save. The old values are overwritten.

How do I revoke Adomo's access to Zoom?

See Revoke the Zoom integration above. In short: set Status to Disabled in Meetings > Agent Config, clear the credentials on the Zoom Configure form, and uninstall the Adomo app from marketplace.zoom.us. Individual users can unlink their own Zoom account from Integrations > Zoom.

What about data retention?

Session records (wake-word hits, agent responses, tool calls, and denials) are kept on the meeting session and visible to admins under Meetings > Sessions. Contact your account team about retention requirements.

Does the agent join meetings without anyone inviting it?

It joins automatically when real-time media starts for a meeting covered by your Adomo Zoom app. If the app isn't installed on a given meeting, the agent doesn't join.

Can I restrict which tools the agent uses for which users?

Tool access is enforced by each user's existing Adomo permissions. To limit what a specific user's agent can do, adjust that user's role and tool access the same way you would for the rest of the Adomo app.