# Webex integrations: meetings, messages and spaces

> Create a meeting and create a space in Webex, and start a workflow when Webex sends “Message created”.

**Canonical page:** https://tray.ai/connectors/webex-integrations/
**Categories:** Communication
**Connects through:** HTTP Connector

## Overview

Webex by Cisco is a collaboration suite for video meetings, team messaging spaces and calling, used by companies for internal and customer communication. Tray.ai connects to Webex through the HTTP Connector, so your workflows can call the Webex API alongside the rest of your stack.

## Use cases

### Meetings

Read, create, update, and delete meetings in Webex from any Tray.ai workflow. The Webex API covers calls such as list meetings and create a meeting.

- List meetings
- Create a meeting
- Get a meeting

### Messages

Read and create messages in Webex from any Tray.ai workflow. The Webex API covers calls such as post a message to a space and get space message history.

- Post a message to a space
- Get space message history

### Spaces

Create spaces in Webex from any Tray.ai workflow. The Webex API covers calls such as create a space and invite people to a space.

- Create a space
- Invite people to a space

### Webex events

Start a Tray.ai workflow the moment something happens in Webex. Webex sends events such as message created and message deleted to a Tray.ai webhook trigger.

- Message created
- Message deleted
- Room created

## Challenges Tray.ai solves

### Keeping Webex credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Webex credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Webex API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Webex API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Webex?

Yes. Tray.ai connects to Webex through the HTTP Connector, which calls the Webex API directly. Any call the Webex API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Webex?

The Webex API uses OAuth 2.0 and a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Webex connector?

Webex runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Webex connector from the Webex API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/