Incident.io
Last updated
Last updated
To integrate groundcover with , follow the steps below. Note that you’ll need a Pro incident.io account with API access.
Generate an API Key Log in to your account and create an API key. Make sure it has at least the “Create incidents” permission.
Set Up the Webhook in groundcover
Set the Webhook URL
to: https://api.incident.io/v2/incidents
Keep the HTTP method as POST
Under Authentication
, select API Key Authentication
and paste the API key you created in step 1.
Create a Workflow
Go to Monitors --> Workflows --> Create Workflow
, and paste the YAML configuration provided below.
Note: The body
section is a dictionary of keys that will be sent as a JSON payload to the incident.io API
Configure the providers
Block
In the providers
block, replace {{ providers.your-incident-io-integration-name }}
with your actual webhook integration name.
For example, if you named your integration test-incidentio
, the config reference would be: {{ providers.test-incidentio }}
Required Parameters for Creating an Incident When triggering an incident, the following keys are required:
idempotency_key
- A unique identifier for the issue (e.g., the issue ID)
visibility
- Defines who can see the incident. Example: "public" (you can adjust this based on your preference)
severity_id
- The ID of the severity level (not the name). You can retrieve this from the . Replace [severity_id]
with your actual value.
name
- Optional but recommended for clearer context
You can include additional optional parameters as needed. Refer to the for the full list of available fields.
Example code for your groundcover workflow:
Another example for a conditional groundcover workflow with your incident.io Webhook (based on the monitor severity):