> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/outbound-integrations/webex.md).
# Cisco Webex Integration
Receive and respond to ilert alerts in Webex.
[Webex](https://www.webex.com/) is the leading enterprise solution for video conferencing, online meetings, screen share, and webinars.
## In ilert: Create the Webex Connector and link it to the alert source
1. In the sidebar, go to **Settings** → **Connectors**.
2. Find **Webex** in the catalogue and click **Connect**.
3. On the next page, choose **Webex** as type, name the connector and click on the save button to authorize ilert App with your Webex account.
4. On the next page, agree with the requested permissions and click on the **Authorize** button
5. In the sidebar, go to **Alerting** → **Alert sources** and open the alert source whose alerts you want to post to Webex. On the **Alert actions** tab, click **Create new alert action**.
6. On the next page choose **Webex** as the type, choose the connector created in step 3, name it, choose **alert events** and the team to publish and click on the **Save** button.
7. Finished! You can now test the connection by clicking on the button **Test this connection**. Thereafter, a test message will be posted on the Webex space.
## FAQ
**Can I link multiple Cisco Accounts to an ilert account?**
Yes.
**Are updates to an alert published on the Webex space?**
Yes, the following updates to an alert are currently being released:
* **Escalations** : An alert is assigned to another user through an automatic escalation.
* **Manual Assignments** : An alert is manually assigned to someone.
* **Actions** : An alert is accepted or resolved.
**Can I choose which updates to an alert will be published in Webex?**
Yes.
---
# 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.ilert.com/integrations/outbound-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.