Webex is a Cisco-powered video conferencing and collaboration platform offering online meetings, webinars, screen sharing, and team messaging
Webex is a Cisco-powered video conferencing and collaboration platform offering online meetings, webinars, screen sharing, and team messaging On Nagent, Webex is exposed as a fully-configurable video conferencing integration that any agent can call — 26 actions, and OAuth authentication. No code is required to wire Webex into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Webex to automate the kinds of tasks video conferencing teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Webex into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Webex, with input parameters and output schema. Drop these into any step of an agent built in Helix.
WEBEX_CREATE_TEAMCreates a new Webex team and automatically adds the authenticated user as a member. Teams are used to organize and group multiple rooms (spaces) under a common umbrella. Use this when you need to create a collaborative workspace for a project, department, or any group that needs multiple related discussion spaces. Note: The creator is automatically added as a team member and can manage team memberships. Use the Team Memberships API to add additional members after creation.
Input parameters
A user-friendly name for the team. Must be non-empty. Can include letters, numbers, spaces, and special characters.
A detailed description of the team's purpose and scope. Optional field that helps team members understand the team's objectives.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_GET_TEAM_DETAILSTool to retrieve details for a specific team by teamId. Use when you need full metadata of a team before performing team-related operations.
Input parameters
The unique identifier for the team.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_LIST_TEAMSLists all teams the authenticated user belongs to. Teams are groups of people with shared rooms visible to all members. Use this when you need to find available teams, get team IDs for other operations, or discover which teams a user has access to. Results are ordered by creation date (newest first) and can be paginated using the max parameter.
Input parameters
Maximum number of teams to return per page. Must be at least 1. Default is 100 if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_LIST_WEBHOOKSLists all webhooks registered for the authenticated user or organization. Supports optional filtering by maximum results and ownership type (creator vs org-wide).
Input parameters
Maximum number of webhooks to return
Filter webhooks by ownership: 'creator' for user-owned, 'org' for org-wide
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_CREATE_MESSAGETool to post a message to a Webex room or person. Use when you have a target roomId or private recipient and want to send text, markdown, files, or card attachments.
Input parameters
Plain-text message content. Maximum 7439 bytes.
List of public URLs for file attachments. Note: Webex API accepts a list but only one file per message is supported.
The room ID to post the message in. Required if sending to a room.
Markdown-formatted message content. Maximum 7439 bytes. When both text and markdown are provided, markdown takes precedence for clients that support it.
The parent message ID to reply to, creating a threaded response.
The person ID for sending a private 1:1 message. Mutually exclusive with roomId.
Content attachments such as Adaptive Cards. Only one card attachment per message is supported.
The email address of the person for a private 1:1 message. Mutually exclusive with roomId.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_CREATE_ROOMCreates a new Webex room for team collaboration. The authenticated user is automatically added as a member. Use this to create group rooms for team discussions or associate rooms with existing teams. To create a 1:1 room, use the Create Message action with toPersonId/toPersonEmail instead. Note: Team rooms cannot be moved after creation. Bots cannot simultaneously create and classify rooms.
Input parameters
A user-friendly name for the room. This will be displayed as the room's title.
The ID for the team with which this room is associated. If specified, the room will be created as part of the team. Team rooms cannot be moved after creation.
Set the space as moderated/locked. When true, only moderators can post messages. Must be true if isAnnouncementOnly is true.
The room is public and therefore discoverable within the org. Anyone can find and join the room. When true, the description field must be filled in.
The description of the space. Required when isPublic is true.
The ID of the space classification to apply during room creation. Note: Bots cannot simultaneously create and classify rooms.
Sets the space into announcement mode. Only moderators can post messages. The space must be locked (isLocked=true) for this to work.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_CREATE_TEAM_MEMBERSHIPTool to add a person to a Webex team by personId or personEmail. Use when granting a user access to a team; requires teamId and one of personId or personEmail.
Input parameters
The team ID to add the person to.
The person ID to add. Required if personEmail is not provided.
Set to true to make the person a team moderator.
The email address of the person to add. Required if personId is not provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_DELETE_MEMBERSHIPTool to delete a Webex membership by its unique identifier. Use when you need to remove a member from a space after confirming the membership exists. Example: "Delete the membership with ID Y2lzY29zcGFjMDczNzA2Njg0ZDliY2YxNDE4NDQyYzQ5NDQzOTExYTk4".
Input parameters
Unique identifier for the membership to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_DELETE_MESSAGETool to delete a Webex message by its unique identifier. Use after confirming the messageId to remove unintended or obsolete messages. Example: "Delete the message with ID Y2lzY29zcGFyazovL21lc3NhZ2UvYWJjMTIzNDU2Nzg5".
Input parameters
Unique identifier for the message to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_DELETE_ROOMDeletes a Webex room by its ID. Deleted rooms cannot be recovered. Note: Non-moderators will be removed from the room instead of deleting it (as a safety measure). Rooms that are part of a team will be archived instead of deleted. Use this when you need to permanently remove a room or leave a room.
Input parameters
The unique identifier for the room to delete. Note: Non-moderators will be removed from the room instead of deleting it. Team rooms will be archived instead of deleted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_GET_MEMBERSHIP_DETAILSTool to retrieve details for a specific membership. Use when you need metadata for a membership by its ID.
Input parameters
The unique identifier for the membership.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_GET_MESSAGE_DETAILSTool to retrieve details for a specific message. Use when you need full content and metadata by message ID.
Input parameters
The unique identifier for the message.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_GET_TEAM_MEMBERSHIP_DETAILSTool to retrieve details for a specific team membership. Use when you need metadata for a team membership by its ID.
Input parameters
The unique identifier for the team membership.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_LIST_MEMBERSHIPSList memberships in Webex rooms. When called without parameters, returns memberships for all rooms the authenticated user belongs to. Use roomId to list all members of a specific room. Use personId or personEmail with roomId to check if a specific person is a member of a room. Supports filtering by teamId and limiting results with max parameter.
Input parameters
Limit the maximum number of membership records returned.
Filter memberships by the Webex room ID. Lists all members of the specified room.
Filter memberships associated with a specific team ID.
Filter memberships by the Webex person ID. Note: Requires roomId parameter to be specified (unless you are a Compliance Officer).
Filter memberships by the member's email address. Note: Requires roomId parameter to be specified (unless you are a Compliance Officer).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_LIST_MESSAGESTool to list messages in a room. Use when you need to retrieve chat history filtered by room, time window, or mentions.
Input parameters
Maximum number of messages to return per request.
Filter messages sent before a specific ISO8601 timestamp.
Unique identifier for the room to list messages from.
Filter messages that are replies to a specific message ID.
Filter messages sent before a specific message, by its ID.
Filter messages where the caller is mentioned; use 'me' or person IDs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_LIST_ROOMSTool to list rooms the authenticated user belongs to. Use after authentication when needing to retrieve spaces filtered by team, type, or sorted. Example: "List my group rooms sorted by last activity."
Input parameters
Filters rooms made public before this ISO 8601 timestamp. Used with orgPublicSpaces.
Maximum number of rooms to return (1-1000). Default is 100.
Filters rooms made public after this ISO 8601 timestamp. Used with orgPublicSpaces.
Filter rooms by type: 'direct' (1:1) or 'group'. Cannot be set in combination with orgPublicSpaces.
Sort results by 'id', 'lastactivity' (recent activity), or 'created' (creation date). Cannot be set in combination with orgPublicSpaces.
Limit rooms to those associated with a specific team by ID. Cannot be set in combination with orgPublicSpaces.
Shows the organization's public spaces (both joined and unjoined). When set, results are sorted by madePublic timestamp. Cannot be combined with teamId, type, or sortBy.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_MESSAGING_LIST_TEAM_MEMBERSHIPSTool to list all memberships for a specific team. Use when you need to retrieve all members of a team, including their roles (moderator status). Requires a valid teamId.
Input parameters
Limit the maximum number of team membership records returned. Default is 100.
The team ID for which to list memberships. Required.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_PEOPLE_GET_PERSONRetrieves detailed profile information for a specific person by their ID. Returns comprehensive user details including contact information, organizational data, presence status, and Webex Calling information. Use when you need full profile details for a known person ID. To find person IDs, use the List People action first.
Input parameters
The unique identifier (ID) of the person to retrieve. This is a base64-encoded identifier that starts with 'Y2lzY29zcGFyazovL3VzL1BFT1BMRS8'. Obtain person IDs from the List People action.
Whether to include Webex Calling (BroadCloud) user details in the response. Set to true to retrieve calling-specific information like extensions and location IDs. Only applicable for users with a Webex Calling license. Default is false.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_PEOPLE_LIST_PEOPLETool to list people in your organization. Use when you need to retrieve people filtered by email, display name, IDs, roles, or location.
Input parameters
List people by ID. Accepts up to 85 person IDs separated by commas.
Maximum number of people to return per request.
List people with this email address. For non-admin calls, either email or displayName is required.
List people in this organization. Only admin users of another organization (such as partners) may use this parameter.
List of role IDs separated by commas.
List people present in this location.
Include Webex Calling user details in the response. Default is false.
List people whose name starts with this string. Note: This parameter may not work for consumer organizations. For non-admin calls, either displayName or email is required.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_ROOMS_GET_ROOM_DETAILSTool to retrieve details for a specific room. Use when you need full metadata of a room before posting messages or updating settings.
Input parameters
Unique identifier for the room.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_UPDATE_MEMBERSHIPUpdates a Webex room membership by ID to change moderator or monitor status. Use this to grant or revoke moderator privileges, or to enable/disable room monitoring for a member. Note: Assigning moderator status requires special account permissions; operations may fail with 403 Forbidden if the authenticated user lacks the necessary entitlements.
Input parameters
Set to true to enable room monitoring for the user, or false to disable monitoring. Monitors can view room content without being active members.
Set to true to make the user a room moderator, or false to remove moderator status. Note: Requires special permissions to assign/remove moderators.
Unique identifier of the membership to update.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_UPDATE_ROOMUpdate a room's title, lock status, or team association. The title parameter is always required by the Webex API - if you're only updating isLocked or teamId, you must still provide the current room title.
Input parameters
User-friendly name for the room. Required by the Webex API even if you're only updating other fields - pass the current title if not changing it.
Unique identifier of the room to update.
Team ID to associate the room with. Use to move the room under a different team.
Lock the room to prevent new users from joining.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_UPDATE_TEAMTool to update a team's name by teamId. Use when you need to rename a Webex team. Example: "Change team 12345 name to 'Project X Team'".
Input parameters
New user-friendly name for the team.
Unique identifier of the team to update.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_WEBHOOKS_CREATE_WEBHOOKCreates a Webex webhook to receive real-time event notifications via HTTP POST requests to your specified URL. Use this tool to register for automated notifications when resources (messages, rooms, memberships, meetings, etc.) are created, updated, deleted, or undergo other state changes. Webhooks enable event-driven integrations without polling. Important: The webhook will be automatically disabled if your target URL fails to respond with HTTP 2xx status codes 100 times within five minutes. Requires 'read' scope for the monitored resource type.
Input parameters
User-friendly name for the webhook.
(Internal) Application ID associated with this webhook.
The event type that triggers the webhook. Supported events: created (object created), updated (object updated), deleted (object deleted), started (meeting started), ended (meeting ended), joined (participant joined), left (participant left), migrated (resource migrated), authorized (authorization granted), deauthorized (authorization revoked), statusChanged (status changed).
Optional filter expression to scope webhook notifications to specific resources. For example, use 'roomId=<id>' to monitor a specific room, or 'hostEmail=<email>' for meetings hosted by a specific user. When using 'ownedBy=org' with filters like hostEmail, hostUserId, ownerEmail, or ownerId, this filter is required.
Optional secret used to generate an HMAC payload signature.
Specifies webhook ownership level. Use 'creator' (default) for personal webhooks that deliver events only to the creating user, or 'org' for organization/admin-level webhooks that deliver events across the entire organization. Org-level webhooks are supported for resources like meetings, recordings, convergedRecordings, meetingParticipants, meetingTranscripts, rooms, and messaging.
The Webex resource type to monitor for events. Supported resources include: messages, memberships, rooms, teams, team_memberships, meetings, recordings, convergedRecordings, meetingParticipants, meetingRecordings, meetingTranscripts, attachmentActions, dataSources, telephony_calls, telephony_conference, telephony_mwi, uc_counters, serviceApp, adminBatchJobs. Creating a webhook requires 'read' scope on the resource being monitored.
The URL that will receive POST event notifications.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_WEBHOOKS_DELETE_WEBHOOKTool to delete a specific webhook. Use when you need to remove an existing webhook by its ID after confirming the identifier.
Input parameters
Unique identifier for the webhook to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEBEX_WEBHOOKS_GET_WEBHOOKRetrieves detailed information about a specific Webex webhook by its ID. Use this action to: - Inspect a webhook's configuration (target URL, resource, event type, filters) - Verify webhook status (active/inactive) - Check webhook ownership and security settings (secret, ownedBy) - Get webhook metadata (creation date, creator, organization) The webhook must exist and be accessible with your current credentials. Returns 404 error if the webhook ID is invalid or you don't have permission to view it.
Input parameters
The unique identifier of the webhook to retrieve. This is the 'id' field returned when creating or listing webhooks. Typically a long base64-encoded string starting with 'Y2lzY29zcGFyazovL'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 79 agents privately built on Nagent that already use Webex.
Build on Nagent
Connect Webex to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Webex, and click "Connect Now." You'll authenticate with OAuth — Nagent handles credential storage and refresh automatically. Once connected, Webex is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Webex is connected, you configure its 26 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Webex steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Webex event fires, the agent kicks off automatically.
Every Webex action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Webex ships with 26 pre-built video conferencing actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Webex together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Webex-based workflows tailored to your business.