Workflow nodes available in ZoomMate
This article lists the workflow nodes available in ZoomMate and describes how each node can be used to build automated workflows across Zoom Workplace and supported third-party applications.
In addition, learn how to use agentic workflows with ZoomMate to streamline tasks, automate processes, and enhance productivity through intelligent workflow automation.
Requirements for using workflow nodes in ZoomMate
- Some features are available with a Zoom Workplace Pro, Zoom Workplace Pro Plus, Zoom Workplace Business, Zoom Workplace Business Plus, Zoom Workplace Enterprise, Zoom Workplace Enterprise Plus, or Enterprise Bundle account
- Show conversational AI enabled
- ZoomMate on the web navigation and Zoom Workplace app navigation bar enabled
- Supported browsers: Chrome, Edge, Safari, or Firefox (latest versions)
- Use of the AI-powered, Third-party connectors, Send SMS message, Send Voice message, Web crawler, and HTTP nodes requires a ZoomMate license and consumes Zoom AI credits.
- Use of the Webhook trigger requires Allow incoming webhooks to trigger agentic workflows to be enabled.
Note: ZoomMate may not be available for select industry verticals and select regional customers.
Available Workflow Nodes
Trigger nodes
Trigger nodes define when your workflow starts, whether by manual button click, scheduled time, meeting event, chat activity, or RSS feed update.
| Node name | Description | Fields that can be managed |
| Manually start |
Manually starts a workflow with a button click
|
|
| Fill out a form | Starts a workflow once a user submits a form |
|
| Meeting event |
Starts a workflow when a meeting event occurs
|
- Meeting event type
- Which meetings to monitor
- Time to offset
|
| Team chat event |
Starts a workflow when a chat event occurs
|
|
| From webhook |
Starts the workflow when a new event is triggered from an external app or service via a webhook, utilizing defined variables
|
- Your webhook URL
- Variables
|
| When link is clicked |
Starts the workflow when someone clicks on a link.
|
- Access
- Zoom chat message
- Preview in Zoom chat
- Your URL will be ready aftert you fill up required fields
|
| Custom schedule |
Starts a workflow according to a predefined schedule (can be manually configured or generated from a prompt)
|
- Frequency
- Starts on
- Time zone
|
| Phone event |
Starts a workflow when a phone event occurs
|
- Missed call event
- SMS event
- Voicemail event
|
| RSS feed |
When a new item is published to an RSS feed
|
- Feed URL
- How often to check for new items
|
Additional notes for using webhooks
If using the From webhook trigger:
- The variables that need to be defined (e.g., incident_id, summary, priority) need to match what is expected from the third-party service that triggers the workflow via webhook.
Note: These variables are available for use in later workflow steps. Variable names must contain only letters, numbers, and underscores. - The workflow must be saved first to obtain the webhook URL (Your webhook URL) to be used within the third-party app or service.
- When testing the workflow, users will be prompted to manually send a sample payload to trigger the workflow. The sample payload can usually be found in the third-party service's webhook support documentation or in tools like Postman to capture live traffic.
AI powered nodes
AI powered nodes leverage artificial intelligence to process, analyze, and transform data within your workflows, enabling intelligent content generation, structured data extraction, and natural language-based decision-making.
| Node name | Description | Fields that can be managed |
| Resource search | Evaluates conditions using natural language logic |
|
| Web search | Perform a web search with selected search engine. |
|
| AI Reasoning | Interprets both system-level and task-level instructions to autonomously reason, retrieve data, and execute actions using connected tools, skills, and knowledge sources |
- Task prompt
- Attach files
- Toolsets*
- Skills
- Max steps
- Output Schema
- Name
- Type
- Description
- Is Array
|
| LLM | Generates content using a large language model based on your instructions. Supports summarization, information extraction, and content generation. |
|
| Extract data | AI interaction node for processing prompts and generating responses with extract json data |
- Content to Extract From
- Additional Context
- Data
|
| AI filter | Evaluates conditions using natural language logic |
|
*Note: The Zoom app tool sets and web search tool are selected in the Reasoning node by default. Users can select additional third-party app tool sets approved by their admins, or unselect any tool set.
Flow control nodes
Flow control nodes provide additional actions to help manage flow and output of a workflow, including creating action-based loops, adding condition-based routing and output, and managing the workflow's final output.
| Node name | Description | Fields that can be managed |
| Loop | Loops an action-based node |
|
| Condition | Establishes a condition to enable the output to follow various paths. Users can turn on AI Condition in this node to describe the condition in natural language. |
- AI Condition
- Condition name
|
| Output |
Ends a workflow with a specified output
|
|
More Tool nodes
Tool nodes that provide additional actions, including searching resources, performing web queries, and sending notifications via SMS/voice messages.
| Node name | Description | Fields that can be managed |
| Form | Generate a survey form submission |
- Form title
- Who can use this form
- Member of specified channels
- Specified users
- Form fields
|
| Custom script |
Insert and run custom Python in your workflow. Code runs in a secure sandbox. The value it returns is mapped to your outputs variables.
|
- Generate or edit with prompt
- Code editor
- Script Input Variables:
- Name
- Type
- Required
- Value to bind
- Script Output Variables:
|
| HTML page |
Build a HTML template to reuse for every workflow runs. At run time, the node injects upstream data, renders the page, and publishes it as a shareable URL.
|
- Generate or edit with prompt
- Template Preview
- Template HTML editor
- Variable used in HTML Template
- Name
- Type
- Required
- Value to bind
|
|
HTTP request
|
Sends an HTTP request to any web service and returns the response to later nodes. You provide a method, URL, and optional headers, query parameters, and body; the node sends the request through a secure outbound proxy and hands back a response object.
|
- Method
- URL
- Query parameters
- Headers
- Body type
- Body
- Timeout
- Credential
- Retry on/off
- Retry count
- Retry interval
- Default value on failure
|
|
Send SMS message
|
Sends a voice message to your phone number*
|
- Phone number
- Message template
- Variables
|
| Web crawler | An automated bot that systemically browses and indexes designated websites for content. |
- Start URL
- Crawl depth
- URL prefix for crawling
|
Notes:
Notes for the HTTP request node:
- The URL is required and must start with
http:// or https://. - Supported methods are GET, POST, PUT, DELETE, PATCH, HEAD, and OPTIONS (defaults to GET).
- Body type can be NONE, JSON, FORM, TEXT, or RAW, and is ignored for GET and HEAD requests.
- Timeout defaults to 10 seconds and cannot exceed 60 seconds.
- Retry count and retry interval are each capped at 5.
- Response bodies larger than 1 MB are rejected and the node returns an error instead of the body.
- Anywhere in the URL, headers, or body you can insert a workflow variable using a placeholder such as
$userId or ${orderId}; the node fills these in from the workflow's data before sending.
HTTP request nodes
When the HTTP request node runs in a published workflow, it executes the request directly and writes a response object into the workflow's data so later nodes can use it. Downstream nodes read it with references such as $response.status_code and $response.body.
The response object contains the following fields:
| Field | Meaning |
|---|
|
success
|
true if the status code was 2xx, otherwise false
|
|
status_code
|
The HTTP status code (for example, 200 or 404)
|
|
body
|
The response body as text
|
|
headers
|
The response headers
|
|
error
|
An error message (present only when something went wrong)
|
Note:
- 5xx responses are treated as failures and will trigger a retry when retries are turned on.
- Responses larger than 1 MB are rejected — the node returns an error instead of the body.
body is always returned as text (a string), even for JSON. Parse it in a later node if you need individual fields.- If the call fails and you set a Default value on failure, that value is returned as the
body so the workflow can continue instead of erroring out.
Body types
The body type controls the Content-Type header and how the body is packaged:
- NONE: no body is sent.
- JSON:
application/json. A string is sent as-is; an object is serialized to JSON. - FORM:
application/x-www-form-urlencoded. Key/value pairs are URL-encoded (for example, a=1&b=2). - TEXT:
text/plain. - RAW:
application/octet-stream.
GET and HEAD requests never send a body; the body settings are skipped for them.
Validate and test the HTTP request node before running
While building, the HTTP request node provides two safety tools:
- Validate: Checks your configuration without sending a real request. It reports errors that block you (missing or invalid method, missing URL, a URL without
http(s):// or without a host, invalid header names, or a negative timeout) and warnings that are just a heads-up (a body type is set but the body is empty, or a JSON body has unbalanced brackets). Placeholders such as $var in the URL are tolerated, so validation won't fail just because a variable isn't filled in yet. - Test: Performs a lightweight connectivity check to your URL and reports the status code and how long it took, a quick way to confirm the host is reachable before wiring everything up. Test calls are rate-limited to 50 per 5 minutes per user.
Authentication with credentials
Rather than typing secrets into headers by hand, save a credential once and reference it from the node. Secrets are stored encrypted and are never shown back in full — previews are masked (for example, Bearer ab****yz). Four credential types are supported:
| Type | What you provide | Header the node adds |
|---|
|
None
| nothing | (no auth header) |
| Bearer | token |
Authorization: Bearer <token>
|
| Basic | username + password |
Authorization: Basic <base64 user:pass>
|
| Custome | header name + header value | |
Zoom Chat nodes
Chat nodes enable you to create, manage, and interact with Zoom Chat within your workflows, whether by sending messages to channels, retrieving message history, creating new channels, or managing channel memberships.
| Node name | Description | Fields that can be managed |
|
Get a channel
|
Retrieves a channel
|
|
|
Get messages
|
Retrieves the message history from a channel
|
|
|
Reply to a message
|
Sends a reply to a message within a message thread
|
- Reply to message
- The message content to send
|
|
Send a message to a channel
|
Sends a message in a channel
|
- Select channel
- Markdown message content
|
|
Send a direct message
|
Sends a direct message to another user
|
|
|
Create a channel
|
Creates a new chat channel
|
- Channel name
- Channel description
- Channel type
- Members to add
|
|
Add people to the channel
|
Adds new members to a channel
|
- Select channel
- Members to add
|
|
Add channel mention group members
|
Adds channel members to a mention group
|
- Action approval
- Channel
- Mention group
- User IDs
|
|
Add contact
|
Sends an invitation to a new contact
|
- Action approval
- Invitee email
- Message
|
|
Create channel mention groups
|
Creates a new mention group within a channel
|
- Action approval
- Channel
- Mention group name
- Description
|
|
Delete channel mention groups
|
Deletes a mention group from a channel
|
|
|
Fetch channel metadata
|
Retrieves a channel's metadata
|
|
|
Fetch inactive channel
|
Retrieves channels that are inactive
|
|
|
Fetch message mentions me
|
Retrieves messages where you have been mentioned
|
- Session
- Include deep link
- Limit
- Sort order
- Start timestamp
- End timestamp
|
|
Fetch message replies
|
Retrieves new message replies
|
- Sessions
- Session
- Limit
- Sort
- Message timestamp
- Reply start timestamp
- Reply end timestamp
|
|
Fetch session metadata
|
Retrieves a chat session's metadata
|
|
|
Fetch session tab
|
Retrieves the resource tabs for a chat or channel
|
|
|
Get channel members
|
Retrieves the members for a channel
|
- Channel
- Member
- Member name
- Page size
|
|
Get channel mention group members
|
Retrieves the members for a mention group
|
|
|
Get channel mention groups
|
Retrieves the mention groups for a channel
|
|
|
Get message deep links
|
Retrieves the deep links for a message
|
- Sessions
- Session
- Message
- Message timestamp
|
|
Get messages
|
Retrieves the message history for a channel
|
|
|
Get session deep links
|
Retrieves the deep links for a session
|
|
|
Get user folders
|
Retrieves the user's chat folders
|
N/A
|
|
Leave channel
|
Leaves a chat channel
|
|
|
List recent sessions
|
List the user's recent chat sessions
|
N/A
|
|
List sent messages
|
Lists the user's sent messages
|
- Start timestamp
- End timestamp
|
|
List unread messages
|
Lists the user's unread messages
|
|
|
Remove channel mention group members
|
Deletes a mention group from a channel
|
- Action approval
- Channel
- Mention group
- User IDs
|
|
Search contacts
|
Searches the user's contacts
|
|
|
Update channel
|
Updates a channel
|
- Action approval
- Channel
- Channel name
- Channel type
- Post message permission
- Mention all permission
- New members can see previous messages and files
|
|
Update channel archive status
|
Updates the archive status for a channel
|
- Action approval
- Action
- Channel ID(s)
|
|
Update channel mute status
|
Updates the notification settings for a channel
|
- Action approval
- Action
- Channel ID(s)
|
|
Update message
|
Updates (edit) the content of a chat message
|
- Action approval
- Chat session
- Message
- Message content
- Message format
|
Note: When the node runs, it looks up the credential and merges its header into your request. If the credential header and one of your own headers have the same name, the credential header wins
Zoom Meeting nodes
Meeting nodes enable you to create, manage, and interact with Zoom meetings within your workflows, whether by scheduling new meetings, updating existing ones, canceling scheduled sessions, or sending messages to meeting participants.
| Node name | Description | Fields that can be managed |
| Create a meeting | Creates a new meeting |
- Select meeting
- Meeting description
- Invitees
- Starts on
- Duration
- Timezone
|
| Update a meeting | Update the details for a previously scheduled meeting |
- Select meeting
- Meeting name
- Meeting description
- Invitees
- Starts on
- Duration
- Timezone
|
| Cancel a meeting | Cancels a previously scheduled meeting |
|
| Send a message to the meeting |
Sends a message to the meeting chat
Note: Sends a message to a meeting chat when the meeting is ongoing. To send a message for an ended meeting chat, use the node in Zoom Chat.
|
- Select meeting
- Message text
- Who can view this message
|
Zoom Task nodes
Task nodes enable you to create, manage, and interact with Zoom Tasks within your workflows, whether by creating new tasks, updating existing ones, assigning tasks to team members, or tracking task completion status.
| Node name | Description | Fields that can be managed |
|
Create a task
|
Creates a new Zoom Task
|
- Title
- Description
- Priority
- Due Date
- Assignee
|
|
Update a task
|
Updates an existing Zoom Task
|
- Title
- Description
- Priority
- Status
|
Zoom Canvas nodes
Canvas nodes enable you to create, update, share, and retrieve Zoom Canvas (formerly Zoom Docs) within your workflows, allowing you to automate document management and collaboration tasks.
| Node name | Description | Fields that can be managed |
| Create a doc |
Creates a new doc
|
- Location
- Title of a new document
- Content
|
| Update a doc | Updates a new doc |
|
| Share a doc | Shares a doc |
- Select doc
- Share to
- Share to user
- Role
- Send notification
- Send chat message
|
| Get a doc | Retrieves info for a doc |
|
Zoom Phone nodes
Using these nodes requires a valid Zoom Phone license.
| Node name | Description | Fields that can be managed |
| Send SMS via Zoom Phone |
Send an SMS message from a Zoom Phone number to one recipient
|
- From
- To (only users' Zoom Phone number and variables from other Zoom Phone nodes can be used in this field)
- Message
|
Zoom Workspace nodes
- Using these nodes requires a valid Zoom Workspace license.
- Workspace nodes may not be available for select industry verticals and select regional customers.
| Node name | Description | Fields that can be managed |
| Create reservation | Create a workspace reservation |
- Workspace Route Key
- Start Time
- End Time
- Time Zone
- Workspace ID
- Delegate User ID
- Meeting ID
|
| Delete workspace reservation | Deletes a workspace reservation |
- Reservation Event ID
- Workspace ID
- Route Account ID
|
| List meetings | List meetings in a time range |
- Start Time
- End Time
- Time Zone
|
| List workspace reservation | List workspace reservations in a time range |
- Start Time
- End Time
- Time Zone
- User IDs
|
| List workspaces | Lists available workspaces based on the filter rules |
- Workspace Route Key
- Location ID
- Location Account ID
- Filter Rule::
- Workspace Type
- Minimum Capacity
- Maximum Capacity
- Required Asset IDs
- Optional Asset IDs
- Availability Check
- Nearby Workspace ID
- Result Size
|
| Search workspace user | Searches workspace users by name |
|
| Search workspaces | Searches workspaces by ID or name |
- Workspace ID
- Workspace Name
- Workspace Type
|
| Update workspace reservation | Update a workspace reservation time |
- Reservation Event ID
- Workspace ID
- Start Time
- End Time
- Time Zone
- Route Account ID
|
| Update workspace reservation | Update a workspace reservation time |
- Reservation Event ID
- Workspace ID
- Start Time
- End Time
- Time Zone
- Route Account ID
|
Third-party nodes
Third-party nodes enable you to integrate external applications and services into your Zoom workflows, whether by connecting to CRM systems like Salesforce, project management tools like Jira, communication platforms like Slack, or productivity suites like Google Workspace and Microsoft 365.
Access to all these
third-party connectors would require ZoomMate license, except Send Email
in Gmail and Outlook which is available unlimited to all paid users (including ZWP paid users).
