Reach Webex From a Workflow or an Agent

What you can do together

• Reach Webex from a workflow or an agent in AI Intelligence Hub through Cisco's own server, with no connector built for it.
• Run one Webex tool as a fixed step in a workflow, or hand an agent the server's tools and let it decide when to call them.
• Scope the token to what the use needs, since it decides what a workflow or an agent reaches in Webex.
• Where retention is the need, scope a connector per engagement that would hold the meetings that matter in Nexus past Webex's own expiry, under a retention schedule you set.

How it connects

The MCP connection is configured once in AI Intelligence Hub with a name, the server URL, the transport and the HTTP headers carrying its credential. Streamable HTTP, Server-Sent Events and WebSocket are the transports carried. The tool list is fetched when the connection binds rather than coded in, and Cisco runs that server under a beta programme, so its tool surface can change; the connection absorbs that because the list is read at bind. In a workflow, an MCP node runs one named tool with arguments fixed at design time. For an agent, the MCP tool hands the model the server's tools, and the model chooses when to call them. What either reaches in Webex is decided by the token carried in those headers.

Retaining recordings is a connector, and it is not prebuilt. Built per engagement on the existing ingestion architecture, it would pull recordings and their available metadata into Nexus on the connector's schedule rather than on Webex events, so a session would be picked up on the next run after it finishes. Each would then be transcribed, indexed and held under the library's access control, retention and audit rather than under Webex's expiry. The engagement would establish which meetings are in scope, because pulling every recording in an organization is both expensive and usually unwanted: most meetings are not records. It would also settle whether the source recording is left, moved or deleted after ingestion.

Webex stays the meeting platform. Scheduling, calling, its own recording and its user management are unchanged, and a connector would write nothing back beyond the post-ingestion action agreed.