Purpose
This guide explains how to configure the Cisco Webex Response integration in Logsign USO, so that Incidents and Alarms can automatically, or an analyst can manually, send a message to a Webex room or directly to a person from a Logsign Incident. This is a notification integration, configured under Settings > Integrations > Responses > +Device.
Prerequisites
- A Webex account and an access token (a bot token is recommended for a persistent integration, since bot tokens do not expire the way personal access tokens do).
Step 1: Create a Webex Bot and Obtain an Access Token
- Log in to the Webex developer portal (developer.webex.com) and create a new bot.
- Copy the bot's access token; treat it as a secret credential.
- Add the bot to the target Webex room (if sending to a room), or note the target person's Webex account email/ID (if sending direct messages).
- If sending to a room, note the room's ID (retrievable via the Webex API or developer portal); if sending to a person, note their person ID or email.
Step 2: Configure the Integration in Logsign USO
In Logsign USO, go to Settings > Integrations > Responses, search for Webex, click Configure then +Device, and fill in:
| Field | Required | Description |
|---|---|---|
| Device Name | Yes | Free-text label identifying this Webex device in Logsign. |
| Access Token | Yes | The bot access token from Step 1. Stored encrypted at rest. |
| Room Id | No | The target room's ID, if sending to a room. |
| To Person Id | No | The target person's Webex ID, if sending a direct message by ID. |
| To Person Email | No | The target person's email, if sending a direct message by email. |
Fill in whichever target field(s) match the method you plan to use; click Create to save the device.
Available Methods
- send_message_to_room — sends a message to the configured Webex room (Room Id). Arg: text (required).
- send_message_to_person — sends a direct message to the configured person (To Person Id or To Person Email). Arg: text (required).
Troubleshooting
| Symptom | Likely cause | What to check |
|---|---|---|
| 401 Unauthorized | Wrong or revoked Access Token. | Re-enter the Access Token exactly as issued for your Webex bot. |
| send_message_to_room fails | The bot has not been added to the target room, or Room Id is wrong. | Confirm the bot is a member of the room and that Room Id matches. |
| send_message_to_person fails | To Person Id/To Person Email is wrong, or the target person has not interacted with the bot before (some Webex configurations require this). | Confirm the target identifier is correct; have the recipient message the bot first if direct messages are being rejected. |
| 429 Too Many Requests | Webex enforces API rate limits per bot/token. | Reduce the frequency of automated messages. |
Notes and Limits
- Configure only the target fields relevant to the method you intend to use; a device configured for room messaging does not need person-target fields filled in, and vice versa.