Communication
Webex for AI agents.
Bring the right space into focus.
Read messages from the Webex spaces a user can access. Prepare grounded team updates and handoffs from the selected conversation.
About Webex
With the Webex connector, your agent reads messages in each user’s own Webex account. It can list the spaces they belong to, read a space’s details, and read the messages in a space, using only the tools your project allows.
Webex is a collaboration platform for meetings, calling and team messaging.
Tools
What your agent can do in Webex.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Webex connection.
-
List spaces
Readwebex_list_spacesFind the spaces available to the connected user.
-
Read a space
Readwebex_get_spaceRetrieve details of one identified space.
-
List messages
Readwebex_list_messagesRead messages in a selected space within an explicit result scope.
-
Read a message
Readwebex_get_messageRetrieve one identified message and its available details.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Webex, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent list spaces and read messages, and switch off
webex_list_messagesif it should only see which spaces exist. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example spaces but not messages. A call outside them is refused.
Get started
Connect Webex
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Webex
Each end user authorizes their own Webex account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Webex account, once. const connection = await agent200 .user("user_123") .connect("webex"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Webex tools
Name the user, the model and the tools. The model decides which Webex tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "List the Webex spaces I am in", tools: ["webex"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Connect the intended Webex account
Have the end user authorize their Webex account through managed OAuth. Select a space the user belongs to before requesting messages.
-
Match scopes to the read task
Webex documents separate permissions for spaces and messages. The connected user’s membership limits the messages available to read.
-
Keep user identity attached
Pass the same authenticated application user through connection and subsequent requests. Keep the Agent200 key in server configuration.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Webex connector and how to use it.
Connector: Webex, through Agent200. In code: "webex". What it does: Read messages from the Webex spaces a user can access. Prepare grounded team updates and handoffs from the selected conversation. Page: https://www.agent200.com/connectors/webex/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Webex's own page, through the authorization link Agent200 returns. Never ask a user for a Webex password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: webex_list_spaces, webex_get_space, webex_list_messages, webex_get_message. Name "webex" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/webex/framework/claude/ https://www.agent200.com/connectors/webex/framework/chatgpt/ https://www.agent200.com/connectors/webex/framework/claude-code/ https://www.agent200.com/connectors/webex/framework/muse/ https://www.agent200.com/connectors/webex/framework/grok-bot/ https://www.agent200.com/connectors/webex/framework/openai-dots/ https://www.agent200.com/connectors/webex/framework/claude-duet/ https://www.agent200.com/connectors/webex/framework/hermes-agent/ https://www.agent200.com/connectors/webex/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/webex.md
Guides
Use Webex with the AI you build on.
Step-by-step setup for Webex with a specific model, assistant or agent framework.
-
Webex + Claude
How to connect Webex to Claude
-
Webex + ChatGPT
How to connect Webex to ChatGPT
-
Webex + Claude Code
How to connect Webex to Claude Code
-
Webex + Muse
How to connect Webex to Muse
-
Webex + Grok Bot
How to connect Webex to Grok Bot
-
Webex + OpenAI Dots
How to connect Webex to OpenAI Dots
-
Webex + Claude Duet
How to connect Webex to Claude Duet
-
Webex + Hermes Agent
How to connect Webex to Hermes Agent
-
Webex + OpenClaw
How to connect Webex to OpenClaw
FAQ
Webex and Agent200, answered.
Which space can the agent read?
Start with a space the connected user belongs to. Identify it by its returned ID; similar space names are not proof of identity. Webex rooms reference.
Does a message list contain the whole conversation?
No. Respect pagination and any result filters. State the time window and space actually retrieved before summarizing; do not treat one page as all history.
Can this workflow post an update?
The listed tools are read operations. A drafted update in the agent answer is not posted to Webex. Sending a message needs a separate write operation and the user’s requested destination.
How do I handle attachments and threads?
Do not claim that file contents or every reply were read from a message summary. Request supported detail through the actual runtime when needed, and label anything not returned.
What permissions should I check?
Confirm the connected user has access to the selected space and the read permissions for rooms and messages. Use the runtime’s advertised tool schema for actual calls; catalogue identifiers are not argument contracts.