> ## 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.

# Setup

> Connect incident.io to Ravenna using an API token from your workspace settings to enable on-call validation and incident management workflows.

<Info>Connect to Incident.io using an API token</Info>

This guide walks you through connecting your Incident.io workspace to enable on-call schedule validation and incident management workflows.

## Prerequisites

Before you begin, ensure you have:

* Admin access to your Incident.io workspace
* An active Incident.io subscription

## Setup guide

<Steps>
  <Step title="Navigate to integrations">
    Go to **Settings > Integrations** and find **Incident.io** under the **Incident Management** section
  </Step>

  <Step title="Select Incident.io">
    Click **Connect** on the Incident.io integration card
  </Step>

  <Step title="Create API token in Incident.io">
    1. Log in to your Incident.io workspace
    2. Navigate to **Settings > API Keys**
    3. Click **Create API Key**
    4. Give your key a descriptive name (e.g., "Workflow Integration")
    5. Select the appropriate scopes:
       * `incidents:read` - Read incident data
       * `schedules:read` - Read on-call schedules
       * `users:read` - Read user information
    6. Click **Create** and copy the API key

    <Warning>
      Save this key securely - you won't be able to see it again
    </Warning>
  </Step>

  <Step title="Configure API token">
    Enter the following information:

    <ParamField path="API Token" type="string" required>
      Your Incident.io API token with the required scopes
    </ParamField>
  </Step>

  <Step title="Complete setup">
    Click **Connect** to complete the integration setup
  </Step>
</Steps>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Connection test fails">
    **Cause**: Invalid API token or insufficient permissions

    **Solution**:

    * Verify your API token is correct
    * Ensure the token has all required scopes (`incidents:read`, `schedules:read`, `users:read`)
    * Check that your Incident.io workspace is active
    * Try creating a new API token
  </Accordion>

  <Accordion title="Actions not appearing in workflows">
    **Cause**: Integration not properly saved or browser cache issue

    **Solution**:

    * Refresh the page
    * Verify the integration shows as "Connected" in Settings
    * Try disconnecting and reconnecting the integration
  </Accordion>

  <Accordion title="On-call validation returns incorrect results">
    **Cause**: Schedule ID is incorrect or user email mismatch

    **Solution**:

    * Verify the schedule ID in Incident.io
    * Ensure user emails match between systems
    * Check the schedule configuration in Incident.io
  </Accordion>
</AccordionGroup>