SoftTech AI Registry
Zoom · ZoomMate

Agentic Work Orchestration

ZoomMate's orchestration layer captures work context from meetings, chats and projects, reasons across Zoom and connected enterprise systems, and executes follow-up work through agentic workflows: assigning tasks, updating systems of record, routing approvals, sending messages and triggering multi-step processes across Zoom and connected third-party applications. Workflow action nodes that perform sensitive write operations can be set to Always ask or Always allow, and administrators can force approval account-wide.

Recorded characteristics

Function
Zoom describes ZoomMate as an AI workspace built into Zoom Workplace that captures context in real time, remembers what matters, and turns decisions into action, organised around three documented functions: Search (agentic search and deep research), Orchestrate (workflows and agents) and Complete (AI-generated deliverables). This record covers the orchestration function and the context gathering and reasoning that feed it. CONTEXT AND REASONING: the ZoomMate workspace unifies meetings, documents, chats and Projects; My Notes is described as the persistent memory layer capturing context from Zoom meetings, third-party meetings and in-person discussions; Agentic Search is described as the retrieval engine across Zoom, the web and connected third-party sources, returning synthesized, cited answers rather than links, with a deep research mode for longer-horizon investigations. ORCHESTRATION AND EXECUTION: Zoom documents agentic workflows as node-based automations built from conversational prompts, templates or a visual low-code builder, running on triggers (events, schedules, webhooks or agentic logic) and automating multi-step actions across Meetings, Chat, Docs and Tasks, plus connected third-party applications. Documented operations include assigning and creating tasks, updating systems of record such as Salesforce opportunities, creating Jira tickets, posting chat and channel messages, sending SMS and voice messages, routing approvals, scheduling follow-ups, generating recurring reports and briefings, and calling any REST API through the HTTP node. Workflows can be attached to Zoom Meetings and to My Notes so that a meeting ending triggers the follow-up work. Activity logs record workflow runs. An AI Reasoning node selects and invokes tool sets to complete a goal. CREATION: generation of slides, sheets, documents and reports through the Zoom AI Productivity Suite is a separate capability area and is recorded here only as an orchestrated outcome, not as this record's function. Zoom also documents Agents: custom-built assistants activated in Zoom chats and channels that can answer questions, take actions and call out to third-party apps. They are noted as part of the ZoomMate architecture and are not recorded as this capability.
Data access
Documented ZoomMate sources: Zoom Meetings content, meeting transcripts and summaries, My Notes (including notes from Google Meet, Microsoft Teams and in-person conversations), Zoom Team Chat and channels, Zoom documents and Projects workspaces, Zoom Tasks, and web content through real-time search and a web crawler node. Connected third-party systems named in current Zoom material include Google Drive, Google Calendar, Gmail, Microsoft OneDrive and Outlook, Microsoft Teams, Salesforce, HubSpot, Jira, Confluence, Slack, ServiceNow, Workday, Zendesk, Asana, Box, Coda, Notion, Linear, Apollo, PagerDuty and Canva, plus arbitrary REST endpoints through the HTTP node. Boundaries: connector availability is not the same as configured access. Zoom documents that account owners and admins must enable third-party app integration, that the user must hold a ZoomMate license, and that the user signs in to each third-party app and grants access before ZoomMate can use it. Zoom states retrieval is permissions-aware and that a user only sees information they already have access to, giving the ServiceNow example of role-based incident access being respected. No claim is made here that any given deployment reaches every listed system. MEMORY AND CONTEXT: Zoom positions My Notes as the persistent memory layer and describes a searchable history of conversations accumulating over time, with notes taggable and shareable, and project workspaces retaining meeting notes, chats, generated artifacts and workflow outputs as a running operational history. Zoom does not publish, in the material reviewed, a retention period, a deletion mechanism specific to ZoomMate memory, or the scope of what is retained versus discarded, so the phrase remembers what matters is not recorded as an unlimited persistent-memory claim.
Actions
Can take actions
External actions
Conditional
Human confirmation
Conditional
Permission basis
User permissions
Administrative control
Documented controls: - Account owners and admins control Show conversational AI, which is a stated requirement for agentic workflows. - Admins enable the ZoomMate tab in web and Zoom Workplace app navigation. - Third-party app integration must be enabled by account owners and admins, and the separate setting AI to perform tasks in third-party apps must be enabled before ZoomMate can act in connected apps; the user must additionally sign in to each app and grant access. - Admins can disable the ability to automatically allow actions and force approval for all sensitive write operations across nodes and tool sets, through the Allow users to disable confirmation for sensitive actions setting. Where the admin has enforced approval, users cannot select Always allow or change a pending action's approval setting. - Webhook triggers require Allow incoming webhooks to trigger agentic workflows to be enabled. - Users can disable, enable, delete, share, export and import workflows; an Activity logs tab lets administrators and workflow owners verify that automations are running as expected. - Workflows deactivate if the owner loses access to a channel used by the workflow or leaves it. - Metered capabilities (AI-powered nodes, third-party connectors, SMS, voice and web crawler nodes) require a ZoomMate license and consume Zoom AI credits, which are separately managed and trackable. Not established: a single documented account-level switch that enables or disables ZoomMate orchestration as a whole, and documented audit retention periods. Custom AI Companion administrative controls are not imported into this record except where Zoom states the same requirement applies to ZoomMate.
Default state
Not established
Availability
Verified against current Zoom first-party material, September 2026. ZoomMate launched 24 June 2026 as a new add-on product; the former AI Companion features remain built into Zoom Workplace under functional names and remain included with eligible paid plans. Zoom states that agentic workflows for ZoomMate are available to paid ZoomMate and Custom AI Companion users in the US, that free users can access a limited version with up to 10 runs per month, and that paid ZoomMate and Custom AI Companion users initially have unlimited runs for a limited time; both test runs and published runs count toward monthly usage. Some features require a Zoom Workplace Pro, Pro Plus, Business, Business Plus, Enterprise, Enterprise Plus or Enterprise Bundle account. Supported browsers are current Chrome, Edge, Safari and Firefox; third-party app integration requires Zoom desktop app 7.0.5 or higher. Zoom notes that ZoomMate may not be available for select industry verticals and select regional customers, and that availability may vary by customer type, region and industry vertical at launch with broader rollout expected through the year. Connector coverage expanded in August 2026 (Canva, Coda, Zendesk, Asana, Box, Microsoft Teams).
Licensing
ZoomMate is a paid add-on sold with included AI Credits for metered AI actions; Zoom's product page lists ZoomMate plans including 2,200 AI credits per user per month for the listed tiers. Advanced capabilities (agentic search, deep research, workflow automation, AI-generated deliverables) are described as metered services consuming AI credits. Pricing is recorded only as an availability fact and is not treated as a capability classification.
External model or provider
Partially established. Zoom documents a federated AI architecture combining proprietary models with third-party LLMs, and specifically documents ZM+ for ZoomMate (August 2026): Anthropic models added to ZoomMate through Amazon Bedrock's managed service, with traffic processed inside Zoom's trust boundary by a designated provider, for select ZoomMate capabilities. Which model or provider executes ordinary ZoomMate orchestration and AI Reasoning steps is not established, and the older AI Companion 3.0 provider list (OpenAI, Anthropic, NVIDIA and Zoom proprietary models) is not copied forward to ZoomMate.
Limitations and uncertainty
ESTABLISHED: ZoomMate is a distinct add-on product, separate from the built-in Zoom Workplace AI features formerly branded AI Companion, and Zoom states Custom AI Companion customers continue to be supported. Zoom Virtual Agent is a separate customer-experience product and none of its customer-service execution (returns, deliveries, purchases, payment or identity workflows) is attributed here. ACTION CLASSIFICATION BASIS: can_take_actions rests on specific documented persistent operations, not the word agentic. Zoom's support documentation names action nodes that perform sensitive write operations such as updating a Salesforce Opportunity and creating a Jira ticket, plus assigning tasks, posting chat and channel messages, sending SMS and voice messages, leaving a channel, and calling arbitrary REST APIs through the HTTP node; workflows deploy to an Active state and run on triggers including meeting completion, schedules and webhooks. EXTERNAL ACTION: conditional. Third-party writes (Salesforce record updates, Jira issue create/update/delete, Confluence and Notion page creation, Asana task creation and assignment, ServiceNow record creation, Zendesk ticket creation, Slack messages, Workday requisition and candidate record management, Google Drive file creation) are documented, but only where an admin has enabled third-party app integration and the task-performing setting, the user holds a ZoomMate license, and the user has signed in to the app and granted access. Search across an external system is not treated as an external action. HUMAN CONFIRMATION: conditional, on positive evidence of both patterns. Action nodes that perform sensitive write operations expose an Action Approval field with Always ask (the workflow cannot complete the action until the user approves it in the ZoomMate or Workflows tab) and Always allow (the workflow completes it without additional approval, and is the default for action nodes that can require approval). AI Reasoning node tool sets default to always ask for approval and can be set to always allow. Admins can force approval account-wide. Initial user instruction to build or run a workflow is not counted as per-action confirmation. PERMISSION BASIS: user_permissions, on positive evidence rather than inference. Zoom states retrieval is permissions-aware and that users only see information they already have access to, giving the ServiceNow role-based access example; third-party execution runs on credentials the individual user supplies by signing in to the app and granting access; and workflows deactivate if the owner loses access to a channel they use. UNRESOLVED: whether scheduled, webhook-triggered or shared workflows continue to execute under the owner's identity in all cases, whether any service or delegated identity is used for background runs, and whether admin-level overrides change the acting principal. No dedicated agent identity is documented. ORCHESTRATION BOUNDARY: where ZoomMate reaches a result through a downstream system, the downstream system performs the operation. ZoomMate is documented as intentionally invoking these tools (AI Reasoning node tool sets, third-party connector nodes, workflow action nodes) to complete the user's stated goal, which is what supports the action classification; capabilities of connected products that ZoomMate is not documented invoking are not attributed to it. Deliverable generation belongs to the Zoom AI Productivity Suite (Slides, Sheets, Paper, Canvas), and custom Agents, Agentic Search as a standalone capability, Custom AI Companion and Zoom Virtual Agent are deliberately excluded from this record. NOT ESTABLISHED: capability-level operational default. Zoom documents several prerequisite settings and a license requirement but does not state what is on or off for a provisioned ZoomMate user, so default_state is not_established rather than disabled; licensing and provisioning are not treated as operational default. CONFIGURATION-DEPENDENT: which systems ZoomMate can read or write, whether an action runs unattended, run limits and metering, and regional, vertical and plan availability.

Evidence