> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/integrations/communications-integrations/webex.md).
# Webex
How Spara integrates with Webex.
Spara can send notifications to Webex channels.
### Step 1: Authentication
{% hint style="info" %}
You must be a Manager- or Integrator-level user to manage third party integrations.
{% endhint %}
Navigate to the [Integrations](https://app.spara.co/organization/integrations) page by clicking on the [Settings](https://app.spara.co/organization) link in the left hand navigation bar.
Click the "Authorize" button. This will lead you through an OAuth authentication flow. There are no further steps necessary upon completing this flow. You should see that the integration is "Enabled" within Spara's Integrations page.
### Step 2: Configure notifications
Once Webex is connected, choose which events notify Webex and which room to send them to from [**Settings > Notifications**](https://app.spara.co/organization/notifications). See [Notifications](/platform/settings/notifications.md).
### Reconnecting Webex
If Webex stops accepting Spara's access (for example, the authorizing account's password changed or the authorization was revoked), the integration shows **Reconnection required** under **Settings > Integrations**, and a To Do asks you to reconnect. Notifications aren't delivered until you do.
Open **Webex** and click **Reauthorize** to sign in again. Your rooms, notification settings, and workflow steps are kept, so nothing needs to be set up again.
---
# 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.spara.com/integrations/communications-integrations/webex.md?ask=&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.
