[Go to site: main page, start]
Skip to main content
Rootly’s Webex integration automatically creates a dedicated meeting bridge for each incident so responders can jump into a call without manual setup. When an incident is declared, a workflow action spins up a Webex meeting and posts the link directly into the incident’s Slack channel.

Automatic Meeting Creation

One Webex meeting per incident, created the moment the workflow triggers.

Dynamic Meeting Names

Set titles using Liquid variables like {{ incident.title }} or {{ incident.severity }}.

Slack-Native

The meeting link is automatically posted to the incident’s Slack channel.

Secure Passwords

Rootly generates a secure password for each meeting automatically.

​
Before You Begin

  • You must have a Webex account (a service account is recommended)
  • You must be a Rootly admin to install the integration
  • The Slack integration should already be configured if you want meeting links posted to incident channels
Rootly recommends installing with a service account (for example, incidents@yourcompany.com) rather than a personal account. This ensures the integration stays active if the installing user leaves the company.

​
Installation

1

Open Integrations

In Rootly, go to Configuration → Integrations and find Webex. Click Setup.
Rootly integrations page showing Webex
2

Authorize in Webex

You’ll be redirected to Webex. Sign in with your Webex account (or create one), then click Allow to grant Rootly access.
Webex OAuth authorization screen
3

Confirm Connection

You’ll be redirected back to Rootly. The integration will show as Connected.
Webex integration connected in Rootly

​
Workflow Actions

The Webex integration unlocks a workflow action that automatically creates a Webex meeting for each incident. If you’re unfamiliar with how workflows function, see the Workflows documentation first.
Webex workflow action in Rootly

​
Create Webex Meeting

This action creates a Webex meeting link for a specific incident.
Rootly enforces one Webex meeting per incident. If this action runs again for the same incident, it will be skipped.
Create Webex Meeting action configuration
​
string
The title of the Webex meeting. Defaults to {{ incident.title }}. Supports Liquid variables.
​
string
The meeting password. Leave blank to have Rootly generate a secure password automatically.
​
string
One or more Slack channels to post the meeting link to. Use {{ incident.slack_channel_id }} to post to the incident channel, or {{ parent_incident.slack_channel_id }} for the parent incident’s channel.
Use the Liquid Variable Explorer to preview what values Liquid variables return before saving your workflow.

​
Uninstall

To remove the Webex integration:
  1. Go to Configuration → Integrations and find Webex
  2. Click Connected to reveal the disconnect option
  3. Click Disconnect
Click Connected to reveal the Disconnect option

​
Frequently Asked Questions

No. Rootly enforces one Webex meeting per incident. If the Create Webex Meeting action runs again for the same incident, it will be skipped.
A free Webex account works for basic meeting creation. However, some meeting features (longer durations, larger participant limits) require a paid Webex plan.
Yes. Use Liquid variables in the Meeting Name field. For example: {{ incident.severity }} - {{ incident.title }} will produce names like SEV1 - Database Outage.
The most common trigger is Incident Created. This creates the meeting immediately when an incident is declared. You can also use Incident Updated if you want to create a meeting only when certain conditions are met (for example, severity escalates to SEV1).
Only one Webex account can be connected at a time per Rootly organization.
Rootly requests OAuth permissions to create meetings on behalf of the connected account. Rootly does not read your existing meetings or contacts.
If the Webex account used during OAuth setup is deactivated, the integration will stop working. Use a shared service account (for example, incidents@yourcompany.com) to avoid this.