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

# Build automations

> Use Copilot to build, edit, validate, and debug Ravenna workflows in plain language with full context about triggers, conditions, and run history.

Automations handle repetitive work for you. Instead of manually triaging every ticket, sending the same follow-up messages, or routing requests to the right team, you describe what should happen and Copilot builds a <Tooltip headline="Workflows" tip="Automated processes and actions" cta="Learn about workflows" href="/documentation/automate/workflows/overview">workflow</Tooltip> that runs automatically.

Describe the automation you want in plain language and Copilot builds it, including triggers, conditions, approval steps, and multi-step logic. When you open Copilot from a workflow page, it automatically has context about that workflow's setup and run history.

<Info>
  Building and editing workflows is available to all workspace members. If you cannot access a workflow, check with your workspace admin.
</Info>

***

## Create workflows

Tell Copilot what you want to automate and it generates the workflow with the right trigger, steps, and settings. You can describe a complete workflow in a single message or build it up step by step.

### What Copilot supports

* **Triggers with filters**: Choose the event that starts the workflow and narrow it to specific conditions (for example, only run when a ticket is created in the IT Support channel with high priority)
* **Conditional branches**: Add steps that follow different paths depending on a condition. For example, check whether a user belongs to a group and take different actions based on the answer
* **Approval steps**: Add approval gates where the workflow pauses and waits for someone to approve or deny before continuing
* **Passing data between steps**: Use information from one step as input to a later step. For example, use the requester's email from the trigger to look up their manager, then send that manager a notification

**Example prompts:**

<Prompt description="Create a workflow that sends a Slack message to #it-ops when a high priority ticket is created in the IT Support channel">
  Create a workflow that sends a Slack message to #it-ops when a high priority ticket is created in the IT Support channel
</Prompt>

<Prompt description="Build a workflow that assigns new tickets in the HR channel to the on-call HR specialist">
  Build a workflow that assigns new tickets in the HR channel to the on-call HR specialist
</Prompt>

<Prompt description="Set up a workflow that closes tickets automatically when they have been in Resolved status for 7 days">
  Set up a workflow that closes tickets automatically when they have been in Resolved status for 7 days
</Prompt>

### Walkthrough: building a simple notification workflow

Start with a straightforward workflow to see how the process works before adding complexity.

<Steps>
  <Step title="Describe what you want to automate">
    <Prompt description="Create a workflow that sends a Slack message to #it-ops when a high priority ticket is created in the IT Support channel">
      Create a workflow that sends a Slack message to #it-ops when a high priority ticket is created in the IT Support channel
    </Prompt>
  </Step>

  <Step title="Copilot builds the workflow">
    Copilot creates the workflow with a "Ticket Created" trigger filtered to the IT Support channel and high priority, followed by a "Send Slack Message" step targeting #it-ops. It automatically configures each step's inputs and validates the workflow before presenting the result.
  </Step>

  <Step title="Review and publish">
    Copilot shows the completed workflow as an interactive card. Click through to the workflow editor to review and publish it.

    <Info>
      Copilot cannot publish or activate workflows directly. After Copilot builds a workflow, you must open the workflow editor to publish it.
    </Info>
  </Step>
</Steps>

### Walkthrough: building a workflow with conditional branching

You can describe workflows with "if this, then that" logic and Copilot sets up the branching for you.

<Steps>
  <Step title="Describe the full workflow">
    Tell Copilot what you want the workflow to do, including the conditions and what should happen in each case.

    <Prompt description={'Create a workflow that runs when a ticket is created. Check if the requester is in the "all-employees" Google group. If they are not a member, add them to the group and post a ticket note confirming they were added. If they are already a member, post a note saying no action was needed.'}>
      Create a workflow that runs when a ticket is created. Check if the requester is in the "all-employees" Google group. If they are not a member, add them to the group and post a ticket note confirming they were added. If they are already a member, post a note saying no action was needed.
    </Prompt>
  </Step>

  <Step title="Copilot builds the workflow">
    Copilot creates the workflow with:

    * A "Ticket Created" trigger
    * A "Check Google Group Membership" step
    * Two paths: one for members already in the group (posts a note) and one for non-members (adds them and posts a confirmation)

    It automatically configures each step's inputs using information from earlier steps (like the requester's email from the trigger) and validates the workflow.
  </Step>

  <Step title="Review and adjust">
    Copilot shows the completed workflow as an interactive card. Click that to navigate to the workflow and click through steps in the editor to review and make any final adjustments.
  </Step>
</Steps>

### Walkthrough: building a workflow with approval

<Steps>
  <Step title="Describe the approval flow">
    <Prompt description="Create a workflow that runs when a Hardware Request ticket is created. If the request is for a MacBook Pro, add me as an approver. If I approve, assign the ticket to the procurement team. If I deny it, close the ticket and post a note explaining why.">
      Create a workflow that runs when a Hardware Request ticket is created. If the request is for a MacBook Pro, add me as an approver. If I approve, assign the ticket to the procurement team. If I deny it, close the ticket and post a note explaining why.
    </Prompt>
  </Step>

  <Step title="Copilot builds the approval workflow">
    Copilot creates the workflow with a condition that checks the hardware type, an approval step on the matching path, and separate actions for the approved and denied outcomes. It configures all step inputs and validates the workflow automatically.
  </Step>
</Steps>

***

## Edit and organize workflows

Update existing workflows by adding, removing, or changing steps. You can also adjust triggers, update conditions, and organize workflows into collections (folders).

**What you can change:**

* Add, remove, or reorder steps in an existing workflow
* Update trigger events and filter conditions
* Change step settings like message content, assignees, or channel targets
* Move workflows between collections to keep them organized
* Rename workflows and update their descriptions

<Info>
  If you are not sure what actions you can add to a workflow, ask Copilot "What workflow actions are available?" and it lists every step type you can use, including integrations like Slack, Google Workspace, and email.
</Info>

**Example prompts:**

<Prompt description="Add an email notification step after the approval step in the New Hire Onboarding workflow">
  Add an email notification step after the approval step in the New Hire Onboarding workflow
</Prompt>

<Prompt description="Update the trigger so the IT Alerts workflow only runs for high priority tickets">
  Update the trigger so the IT Alerts workflow only runs for high priority tickets
</Prompt>

<Prompt description={'Create a workflow collection called "Notifications" for all alert-related workflows'}>
  Create a workflow collection called "Notifications" for all alert-related workflows
</Prompt>

<Prompt description={'Move the "IT Alerts" workflow to the "Notifications" collection'}>
  Move the "IT Alerts" workflow to the "Notifications" collection
</Prompt>

<Prompt description="Remove the Slack notification step from the Offboarding workflow">
  Remove the Slack notification step from the Offboarding workflow
</Prompt>

***

## Validate workflows

Before turning on a workflow, ask Copilot to check it for common problems like missing triggers, disconnected steps, or invalid references between steps.

**Example prompts:**

<Prompt description="Check the New Hire Onboarding workflow for issues">
  Check the New Hire Onboarding workflow for issues
</Prompt>

<Prompt description="Is the IT Alerts workflow ready to turn on?">
  Is the IT Alerts workflow ready to turn on?
</Prompt>

***

## Troubleshoot workflow runs

When a workflow run fails or does something unexpected, Copilot can pull up the full run history, show you which steps succeeded, which failed, and what the error was.

**Example prompts:**

<Prompt description="Why did the last run of the Onboarding workflow fail?">
  Why did the last run of the Onboarding workflow fail?
</Prompt>

<Prompt description={'Show me recent runs for the "IT Alerts" workflow'}>
  Show me recent runs for the "IT Alerts" workflow
</Prompt>

***

## Tips

* **Start simple.** If you are new to workflows, begin with a single trigger and one or two steps. You can always ask Copilot to add more steps later.
* **Describe the complete workflow in one message** when possible. Copilot handles triggers, branches, and step configuration all at once, which works better than adding pieces one at a time.
* **Open Copilot from the workflow page** to give it automatic context about the workflow you are editing or troubleshooting.
* **Validate before publishing.** Ask Copilot to check for issues before opening the workflow editor to publish it.
* **Ask what actions are available.** If you are not sure what steps you can add, ask "What workflow actions are available?" and Copilot lists them, including available integrations.

<Callout icon="link" color="#6B7280">
  Learn more about [configuring your workspace](/documentation/automate/copilot/configure-workspace), [workflows](/documentation/automate/workflows/overview), [building workflows](/documentation/automate/workflows/publish), and [workflow collections](/documentation/automate/workflows/collections)
</Callout>