Skip to content
ClickRuntime

Automate incident.io

Keep track of incidents without refreshing incident.io all day: hear when one is declared, get a weekly roll-up by severity, send stakeholders a recap once an incident is resolved, and chase post-incident follow-ups that nobody has closed. Tell your AI assistant what you need, review the plan it shows you, and the automation then runs on its own.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: check incident.io every 5 minutes and email me at oncall@acme.com whenever a new incident is declared, with its name, severity and link.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in incident.io

Alerts when an incident is declared, recaps once it is resolved, and weekly reports on severity and unfinished follow-ups. These are ready-made starting points. Anything else you can describe works too.
Every 5 minutes

Get an email when an incident is declared

Within a few minutes of a new incident in incident.io, you get an email with its name and severity.

See how it works
Weekly

Get a weekly incident report by severity

Each Monday you see last week's incidents grouped by severity, with status and how long each lasted.

See how it works
Every 15 minutesAI

Send a short recap when an incident is resolved

Once an incident closes, stakeholders get a plain summary of what happened, built from its updates.

See how it works
Weekly

Chase unfinished post-incident follow-ups

Every week you get the follow-ups still outstanding, grouped by owner, with how long each has been open.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with incident.io, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any incident.io automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what incident.io should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every Friday, summarize this week's incident.io incidents by severity and list any without a follow-up action assigned.

When an incident.io incident is declared, add a row to our incident log in Google Sheets.

When an incident.io incident is resolved, create Jira tickets for each follow-up, add the summary to our Notion incident page, and post the links to Slack.

Beyond chat

Have incident.io work when you're not in the chat

Connecting incident.io to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect incident.io

incident.io connects with an API key you create in your own incident.io settings. The permissions you pick for the key decide what ClickRuntime can read.

incident.io

Developer / Incident management

  1. In incident.io, open Settings, then API keys, and choose Create. You need the api_keys_manage permission to do this.
  2. Pick the permissions the automation needs, for example viewing incidents and follow-ups. They can't be changed after the key is created.
  3. Copy the key straight away, because incident.io shows it only once.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the key as a secret for incident.io.

Good to know

incident.io limits that affect automations

  • Each API key can make 1,200 requests per minute, which is plenty for polling incidents every few minutes.
  • A key's permissions are fixed when it is created. If an automation later needs more access, create a new key and replace the saved secret.
  • The key is displayed once at creation, so keep it until it is saved in ClickRuntime.

FAQ

Questions about automating incident.io

What can ClickRuntime read in incident.io?
Whatever the API key's permissions allow. The ready automations only read: incidents, their updates and follow-ups. Nothing is declared or changed in incident.io.
How quickly will I hear about a new incident?
The new-incident alert checks every 5 minutes and remembers which incidents it has already told you about, so each one is reported once.
Is AI needed for the incident recap?
The resolved-incident recap uses AI to summarise the updates. That AI is included in every ClickRuntime plan, so you don't add a key of your own. The alerts and weekly reports run without AI.
How are follow-ups grouped in the weekly list?
Outstanding follow-ups are grouped by assignee and show how long each has been open, counted from when it was created, since follow-ups have no due date field.
Can I change what the key can access later?
Not on the same key. incident.io locks permissions at creation, so you make a new key with the right permissions and update the secret in the ClickRuntime dashboard.
Is this a incident.io connector for ChatGPT or Claude?
Not for chatting with incident.io data. A chat connector lets your assistant read and change incident.io while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each incident.io event.

Related pages

Keep exploring

Tell your assistant what incident.io should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude