Connect to Incident.io using an API token
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
- Log in to your Incident.io workspace
- Navigate to Settings > API Keys
- Click Create API Key
- Give your key a descriptive name (e.g., “Workflow Integration”)
- Select the appropriate scopes:
incidents:read- Read incident dataschedules:read- Read on-call schedulesusers:read- Read user information
- 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:
Your Incident.io API token with the required scopes
5
Complete setup
Click Connect to complete the integration setup
Troubleshooting
Connection test fails
Connection test fails
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
Actions not appearing in workflows
Actions not appearing in workflows
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
On-call validation returns incorrect results
On-call validation returns incorrect results
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
Features
Once connected, you can use Incident.io actions in workflows:
Incident.io Actions
Validate on-call membership to route tickets to the right engineers based on schedules