Skip to main content

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.

Connect to Incident.io using an API token
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

1

Navigate to integrations

Go to Settings > Integrations and find Incident.io under the Incident Management section
2

Select Incident.io

Click Connect on the Incident.io integration card
3

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
Save this key securely - you won’t be able to see it again
4

Configure API token

Enter the following information:
​
API Token
string
required
Your Incident.io API token with the required scopes
5

Complete setup

Click Connect to complete the integration setup

​
Troubleshooting

Cause: Invalid API token or insufficient permissionsSolution:
  • 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
Cause: Integration not properly saved or browser cache issueSolution:
  • Refresh the page
  • Verify the integration shows as “Connected” in Settings
  • Try disconnecting and reconnecting the integration
Cause: Schedule ID is incorrect or user email mismatchSolution:
  • Verify the schedule ID in Incident.io
  • Ensure user emails match between systems
  • Check the schedule configuration in Incident.io