> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows

> Automatically create Webex meeting links for incidents using Rootly workflow actions, with attendee invitations and links shared in Slack channels.

## Overview

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](/workflows/workflows) documentation first.

<Frame>
  <img alt="Webex workflow action in Rootly" src="https://mintcdn.com/rootly/ljLqQxzWDg3HgLpA/images/integrations/webex/workflows/images-1.webp?fit=max&auto=format&n=ljLqQxzWDg3HgLpA&q=85&s=f40799eef4c65337c0c7c4a97b55df95" width="879" height="491" data-path="images/integrations/webex/workflows/images-1.webp" />
</Frame>

## Available Actions

### Create Webex Meeting

This action creates a Webex meeting link for a specific incident.

<Warning>
  Rootly enforces one Webex meeting per incident. If this action runs again for the same incident, it will be skipped.
</Warning>

<Frame>
  <img alt="Create Webex Meeting action configuration" src="https://mintcdn.com/rootly/ljLqQxzWDg3HgLpA/images/integrations/webex/workflows/images-2.webp?fit=max&auto=format&n=ljLqQxzWDg3HgLpA&q=85&s=efdf37051aa6dadc8fc8bce1f2c0cab1" width="892" height="506" data-path="images/integrations/webex/workflows/images-2.webp" />
</Frame>

<ParamField body="Meeting Name" type="string">
  The title of the Webex meeting. Defaults to `{{ incident.title }}`. Supports [Liquid variables](/liquid/incident-variables).
</ParamField>

<ParamField body="Password" type="string">
  The meeting password. Leave blank to have Rootly generate a secure password automatically.
</ParamField>

<ParamField body="Slack Channels" type="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.
</ParamField>

<Tip>
  Use the [Liquid Variable Explorer](https://rootly.com/account/help/liquid-explorer) to preview what values Liquid variables return before saving your workflow.
</Tip>

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Can I customize the meeting name per incident type?" icon="heading">
    Yes. Use Liquid variables in the **Meeting Name** field. For example: `{{ incident.severity }} - {{ incident.title }}` will produce names like `SEV1 - Database Outage`.
  </Accordion>

  <Accordion title="What trigger should I use for this action?" icon="bolt">
    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 (e.g., severity escalates to SEV1).
  </Accordion>

  <Accordion title="How do I make sure the meeting link appears in Slack?" icon="plus">
    Set the **Slack Channels** field to `{{ incident.slack_channel_id }}`. This requires the Slack integration to be installed and a channel to already exist for the incident (typically created by a separate workflow action earlier in the same workflow).
  </Accordion>
</AccordionGroup>
