Skip to main content
Integrations · Zoom
A Guild agent can schedule meetings, provision phone users, and pull live dashboard metrics directly in Zoom on your team’s behalf. Guild stores the Zoom access token server-side so agent code never sees it, and credential policies let you restrict exactly which operations each agent may call.

Book a demo

See how teams govern agents that use Zoom.

Talk to sales

Get access to Guild, then connect Zoom to your first agent.

What the Zoom integration exposes

The tools cover meetings, webinars, users, Zoom Phone configuration, call queues, shared line groups, Zoom Rooms, chat channels, and account and billing management for master and sub accounts. Dashboard tools return participant quality-of-service data, client feedback, and usage reports for meetings, webinars, and phone. Tools are named with the zoom_openapi_ prefix and imported from guildai~zoom-openapi. Use pick() to include only the tools your agent needs.

How it works

1

Open credentials in Guild

Go to your account or organization and open Access & setup > Credentials. See Credentials for workspace, member, and agent-scoped options.
2

Connect the Zoom integration

Click Connect, select zoom-openapi, and paste your Zoom access token into the API Key field. Guild sends it as a bearer token in the Authorization header on every agent request.
3

Add tools to your agent

Import ZoomOpenapiTools from @guildai-services/guildai~zoom-openapi and spread it into your agent’s tools object. Use pick() to limit the agent to the specific operations it needs.

Why Zoom access needs governing

Zoom tools can create and disassociate sub accounts, cancel billing plans, delete users, and modify phone routing for an entire organization. Guild’s credential proxy enforces credential policies before any request leaves Guild: DENY rules block specific operations or HTTP methods outright, and ALLOW rules can be scoped to individual agents or workspaces, so a reporting agent that only reads dashboard metrics cannot also delete call queues. Credentials are injected server-side after the policy check passes, so agent code never handles the token directly. The catalog notes the Zoom access token expires after about an hour; rotating it in Guild takes effect immediately across every agent using that credential. Without policies the credential starts with an allow-all default; adding scoped rules and removing the default turns that into an explicit deny for anything not covered.

About the Zoom integration

Agents can create and manage Zoom meetings, webinars, and users, as well as configure phone settings, call queues, shared line groups, and Zoom Rooms. They can also retrieve dashboard metrics and reports for meetings, webinars, and phone usage. Account and billing management for master and sub accounts is also supported. The integration is guildai~zoom-openapi.

Authentication

  • Type: API key
  • Header: Guild sends the key as a bearer token in the Authorization header

Setup

1

Connect Zoom

In Guild, go to Access & setup > Credentials, click Connect, select zoom-openapi, and paste the key into API Key.
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Selecting specific tools

Tools are named with the zoom_openapi_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~zoom-openapi:

Frequently asked questions

No. The catalog entry lists no webhook events for this integration, so agents cannot trigger on Zoom events through Guild.
Write a DENY rule in credential policies that targets billing operations and scopes it to the agent that should be blocked. A DENY rule always wins over an ALLOW rule, so the meeting agent can keep broad access while the billing tools stay off-limits.
Yes. Connect a workspace-scoped credential from the workspace’s Credentials page and choose The whole workspace. Guild will use that credential for agents in that workspace instead of the account-level one, as described in Credentials.
No. Guild stores the token and adds it server-side through its credential proxy. Agent code never receives or logs the token.

Put a governed agent on Zoom this week

Book a demo

See how teams govern agents that use Zoom.

Talk to sales

Get access to Guild, then connect Zoom to your first agent.
Also runs on Guild: Discord · Email · Gmail · SendGrid Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 20, 2026