> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/cisco-webex.md).

# Cisco Webex

Connect to Cisco Webex to send messages, create rooms and meetings, and read meeting recordings and transcripts via the Webex REST API.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector   | Authentication |
| ----------- | -------------- |
| Cisco Webex | Access Token   |

#### Cisco Webex

Connect to Cisco Webex to send messages, create rooms and meetings, and read meeting recordings and transcripts via the Webex REST API.

**Set up in Cisco Webex**

1. Sign in to the Webex Developer Portal at <https://developer.webex.com>.
2. Open the Getting Started page and copy your Personal Access Token from the Authentication section.
3. Note: personal access tokens expire about 12 hours after you sign in and are intended for testing. For production, create a Webex integration or service app to obtain a longer-lived OAuth token.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Cisco Webex**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Access Token  | Yes      | A Webex Bearer token — the only credential needed (your Webex org is inferred from the token, so there is no separate org field). Pick the token by which actions you need. Bot token (developer.webex.com > My Webex Apps > Create a Bot): Send Message and Create Room only — bots cannot access meetings, recordings, or transcripts. Personal Access Token (developer.webex.com, avatar menu > Copy): all actions, but expires after 12 hours and must come from a licensed (non-bot) user — best for testing. Service App or Integration (OAuth) token: for production — it must grant meeting:schedules\_write, meeting:recordings\_read, meeting:transcripts\_read, and meeting:schedules\_read to run the meeting, recording, and transcript actions. Do not use a Webex 'agentic' token: those target the Webex MCP API, not the REST v1 API this integration uses, and will fail every action. [Provider instructions](https://developer.webex.com/docs/bots). |

**Provider documentation:** [Setup reference](https://developer.webex.com/docs/getting-your-personal-access-token).

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Cisco Webex** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Send Message

Send a message to a Webex room or directly to a person.

**Required permissions:** `spark:messages_write`.

**Inputs**

| Field           | Type            | Required | Description                                                                                           |
| --------------- | --------------- | -------- | ----------------------------------------------------------------------------------------------------- |
| Room            | select (string) | No       | Pick a room (space) from the dropdown, or enter a room id. Options load from the selected connection. |
| To Person Email | string          | No       | Email of the person to direct-message.                                                                |
| To Person ID    | string          | No       | ID of the person to direct-message.                                                                   |
| Text            | textarea        | No       | Plain-text message body.                                                                              |
| Markdown        | textarea        | No       | Markdown message body (rendered by Webex clients).                                                    |

**Outputs**

| Field      | Type   | Description                                      |
| ---------- | ------ | ------------------------------------------------ |
| Message ID | string | The id of the sent message.                      |
| Room ID    | string | The id of the room the message was posted to.    |
| Created    | string | ISO 8601 timestamp when the message was created. |

#### Create Room

Create a new Webex room (space), optionally inside a team.

**Required permissions:** `spark:rooms_write`.

**Inputs**

| Field   | Type   | Required | Description                                        |
| ------- | ------ | -------- | -------------------------------------------------- |
| Title   | string | Yes      | Name for the new room.                             |
| Team ID | string | No       | Optional team id to create the room within a team. |

**Outputs**

| Field   | Type   | Description                                   |
| ------- | ------ | --------------------------------------------- |
| Room ID | string | The id of the created room.                   |
| Title   | string | The title of the created room.                |
| Created | string | ISO 8601 timestamp when the room was created. |

#### Create Meeting

Schedule a Webex meeting with a title, start, and end time.

**Required permissions:** `meeting:schedules_write`.

**Inputs**

| Field          | Type     | Required | Description                                           |
| -------------- | -------- | -------- | ----------------------------------------------------- |
| Title          | string   | Yes      | Meeting title.                                        |
| Start          | string   | Yes      | Start time in ISO 8601 (include a UTC offset).        |
| End            | string   | Yes      | End time in ISO 8601 (include a UTC offset).          |
| Timezone       | string   | No       | IANA timezone name for the meeting.                   |
| Agenda         | textarea | No       | Optional meeting agenda (max 1300 characters).        |
| Password       | string   | No       | Optional meeting password. Auto-generated if omitted. |
| Invitee Emails | string   | No       | Comma-separated invitee email addresses.              |

**Outputs**

| Field          | Type   | Description                       |
| -------------- | ------ | --------------------------------- |
| Meeting ID     | string | The id of the created meeting.    |
| Title          | string | The title of the created meeting. |
| Web Link       | string | Join URL for the meeting.         |
| Meeting Number | string | The dial-in meeting number.       |
| Start          | string | Scheduled start time (ISO 8601).  |
| End            | string | Scheduled end time (ISO 8601).    |

#### List Meeting Recordings

List Webex meeting recordings, optionally filtered by meeting or date range.

**Required permissions:** `meeting:recordings_read`.

**Inputs**

| Field       | Type    | Required | Description                                                                          |
| ----------- | ------- | -------- | ------------------------------------------------------------------------------------ |
| Meeting ID  | string  | No       | Filter recordings to a specific meeting id.                                          |
| From        | string  | No       | Start of the time window (ISO 8601).                                                 |
| To          | string  | No       | End of the time window (ISO 8601).                                                   |
| Host Email  | string  | No       | List recordings for this host (admin tokens only).                                   |
| Max Results | integer | No       | Maximum recordings to return (default 100). Minimum: 1. Maximum: 1000. Default: 100. |

**Outputs**

| Field          | Type          | Description                          |
| -------------- | ------------- | ------------------------------------ |
| Recordings     | object\_array | The recordings matching the filters. |
| Recording IDs  | array         | List of recording ids returned.      |
| Returned Count | integer       | Number of recordings returned.       |

#### Get Meeting Transcript

Download a Webex meeting transcript by transcript id or meeting id.

**Required permissions:** `meeting:transcripts_read`, `meeting:schedules_read`.

**Inputs**

| Field         | Type   | Required | Description                                               |
| ------------- | ------ | -------- | --------------------------------------------------------- |
| Transcript ID | string | No       | Download this specific transcript id.                     |
| Meeting ID    | string | No       | Download the first available transcript for this meeting. |
| Format        | string | No       | Transcript format: 'vtt' (default) or 'txt'.              |

**Outputs**

| Field         | Type   | Description                                  |
| ------------- | ------ | -------------------------------------------- |
| Transcript ID | string | The id of the downloaded transcript.         |
| Meeting ID    | string | The meeting id the transcript belongs to.    |
| Format        | string | The format the transcript was downloaded in. |
| Content       | string | The transcript text.                         |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/cisco-webex.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
