incident.io is a Slack-native incident management platform. Connecting incident.io to Paradime automatically creates incidents in incident.io whenever a Bolt schedule fails, so your team can track and resolve dbt™ pipeline issues through your existing on-call and postmortem workflows.
What you can do
- Automatically create incidents when dbt™ runs fail
- Leverage Slack-native incident management workflows
- Track MTTR and incident frequency for data pipelines
- Integrate pipeline failures with your on-call rotation
- Maintain centralized incident tracking across your organization
- Use incident.io’s timeline and postmortem features for pipeline issues
Paradime uses the incident.io API to automatically create incidents for Bolt Schedules.
Prerequisites
Before connecting incident.io to Paradime, make sure you have:
- An existing Bolt schedule
- incident.io account with API access
- incident.io API Key
- Configured severity levels in incident.io
1. Generate API Key
Important: Store your API key securely. You will need it to configure the Paradime integration.
Step 2: Connect incident.io to Paradime
- In Paradime, go to Settings → Integrations (see connecting integrations), and find incident.io.
- Paste your incident.io API Key into the field provided.
- Click Create to establish the connection.
Once connected, Paradime will automatically create incidents in incident.io whenever Bolt runs fail.
Step 3: Enable incident.io for your Bolt schedules
After enabling the integration, you can configure which Bolt Schedules should create incidents in incident.io when they fail.
To configure incident creation:
- Navigate to Bolt > Schedules in the Paradime interface.
- Select the schedule you want to monitor.
- Open the Integration Settings for that schedule.
- Enable incident.io Incident Creation to automatically create incidents in incident.io when the schedule fails.
Once enabled, any failures in the configured Bolt Schedules will automatically trigger incident creation in incident.io, allowing your team to respond quickly to data pipeline issues.