incident.io + Stream Deck
developer-tools · 0 triggers · 86 actions
Incident management and response platform Add incident.io to your Stream Deck workflows with guided setup for the connection details it needs.
- No code
- Free tier
- One Stream Deck press
- Pairs with OBS & Elgato tools
- OAuth & keys handled in-builder
Popular ways to use incident.io
Add incident.io to a workflow and pair it with a Stream Deck button to run it in one press — handy for developer-tools tasks. Combine it with OBS, your Elgato tools, or any other app you connect to build a routine that fits how you work.
Browse all templatesTriggers & actions
Steps your workflow can perform in incident.io.
Create Incident V2
Tool to create a new incident in incident.io using the V2 API. Use when you need to report and track an operational issue or outage. Requires at minimum an idempotency_key and visibility setting. Optionally specify severity, incident type, custom fields, role assignments, and other attributes.
Edit Incident V2
Tool to edit an existing incident in incident.io. Use when you need to update incident details like name, summary, severity, status, custom fields, or role assignments.
Get Incident by ID (V2)
Tool to retrieve a specific incident by ID using V2 API. Use when you need detailed information about an incident including duration metrics, timestamps, and workload data.
List Alert Sources V2
Tool to list all configured alert sources in incident.io. Use when you need to retrieve alert sources that send alerts to incident.io for routing.
List Alerts V2
Tool to list alerts from incident.io. Use when you need to retrieve alerts for the organisation with pagination support.
List Catalog Entries V3
Tool to list entries from a catalog type in incident.io. Use when you need to retrieve catalog entries for a specific catalog type with pagination and filtering support.
List Catalog Types V3
Tool to retrieve all catalog types configured for an organization using V3 API. Use when you need to list available catalog types or understand the catalog schema structure. This includes both synced types backed by external resources and custom catalog types.
List Incident Roles V2
Tool to list all incident roles for an organization using V2 API. Use when you need to retrieve available incident roles and their configurations.
About incident.io
Incident management and response platform
developer-tools
How to connect
1
Sign up for free
Create your Conductor Deck account: no credit card required.
2
Connect incident.io
Follow the setup prompts for incident.io. Conductor Deck handles the app authorization or required connection details inside the workflow builder.
3
Build a workflow
Add an incident.io action to your visual workflow canvas. Configure the options you need, then connect it to other steps.
4
Assign to Stream Deck
Sync your workflow to any Stream Deck button. Press once to trigger the entire sequence.
Frequently asked questions
- How do I connect incident.io?
- Sign up for Conductor Deck, then add a incident.io step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.
- Is it free?
- Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.
- What's the difference between a trigger and an action?
- A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.
Automate incident.io with your Stream Deck
Sign up for free and start building incident.io workflows in minutes.