Attach link
WriteAttach a link, like the NodeHub ticket, to an incident.
Permissions and limits
Account permissions
- Edit incidents
A repeated request may repeat the external action. Review the previous result before retrying a write.
Alerting & Incidents · CONNECTIONincident.io + NodeHub
Declare incidents from tickets and follow them to resolution.
Explore 15 workflow actions for incident.io, including account permissions and operation limits.
11 read actions4 write actions
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Declare an incident.io incident for the ticket
WriteCreate an incident.io incident from the run's ticket and link it there, where its status stays current. Sent once: a lost answer is checked with the vendor, never sent again.
Permissions and limits
Account permissions
Depends on the connected account and selected operation. Check the service documentation.
Operation limits
- Needs a ticket: a run without one fails before anything is sent.
- Sent once. A lost answer leaves the step uncertain: NodeHub checks with the vendor, read only, and never sends it again.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Declare incident
WriteDeclare an incident with a name, summary, severity and type. incident.io may page people on call.
Permissions and limits
Account permissions
- Create incidents
Operation limits
- incident.io allows 300 creates an hour, or 10 when it opens a Slack or Teams channel.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Get catalog entry
ReadRead one exact catalog entry and its catalog type without exposing attributes or aliases.
Permissions and limits
Account permissions
- View data
Get catalog type
ReadRead native catalog type identity and typed attribute schema for fixed-filter validation.
Permissions and limits
Account permissions
- View data
Get custom field
ReadRead one exact custom-field schema, including catalog binding and filtering rules.
Permissions and limits
Account permissions
- View data
Get custom-field option
ReadRead one exact option and its owning custom field.
Permissions and limits
Account permissions
- View data
Get incident
ReadRead an incident: its name, status, severity and link.
Permissions and limits
Account permissions
- View data
Link an existing incident.io incident to the ticket
WriteLink an existing incident.io incident to the run's ticket by its ID. Its status stays current on the ticket.
Permissions and limits
Account permissions
Depends on the connected account and selected operation. Check the service documentation.
Operation limits
- Needs a ticket: a run without one fails before anything is sent.
- Sent once. A lost answer leaves the step uncertain: NodeHub checks with the vendor, read only, and never sends it again.
A repeated request may repeat the external action. Review the previous result before retrying a write.
List catalog entries
ReadRead one bounded page from the custom field catalog type.
Permissions and limits
Account permissions
- View data
Pagination: cursor. Check the result for additional pages; a single action may not return every record.
List custom fields
ReadRead the account custom-field schemas without guessing team or service fields.
Permissions and limits
Account permissions
- View data
List custom-field options
ReadRead one bounded page of options belonging to an exact custom field.
Permissions and limits
Account permissions
- View data
Pagination: cursor. Check the result for additional pages; a single action may not return every record.
List incident types
ReadRead the incident types, and which one is the default.
Permissions and limits
Account permissions
- View data
List incidents
ReadRead incidents, newest first, one page at a time.
Permissions and limits
Account permissions
- View data
Operation limits
- incident.io allows 60 incident lists a minute per key. A private incident shows only to a key that may see it.
Pagination: cursor. Check the result for additional pages; a single action may not return every record.
List severities
ReadRead the severities an incident can have, with their rank.
Permissions and limits
Account permissions
- View data
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in incident.io. A saved workflow is not a completed provider action.
EXPLORE YOUR STACK
