Declare Rootly incidents from tickets and follow their status.
Explore 14 workflow actions for Rootly, including account permissions and operation limits.
7 read actions7 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.
Add timeline event
Write
Add an event to an incident's timeline, like a link back to the NodeHub ticket.
Permissions and limits
Account permissions
Update the selected incident
A repeated request may repeat the external action. Review the previous result before retrying a write.
Create incident
Write
Create a named incident and attach affected services and teams.
Permissions and limits
Account permissions
Create incidents
Operation limits
Rootly may run configured incident workflows and notify responders when incidents are created or updated.
Making an incident private cannot be undone in Rootly.
Returns typed resource summaries. Embedded integrations, arbitrary catalog properties, alert email addresses and included resources are excluded.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Create service
Write
Create a service catalog entry with explicit dependencies and owners.
Permissions and limits
Account permissions
Create services
Operation limits
Returns typed resource summaries. Embedded integrations, arbitrary catalog properties, alert email addresses and included resources are excluded.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Declare a Rootly incident for the ticket
Write
Create a Rootly 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.
Get incident
Read
Read the status and summary of one incident.
Permissions and limits
Account permissions
Read the selected incident
Operation limits
Returns typed resource summaries. Embedded integrations, arbitrary catalog properties, alert email addresses and included resources are excluded.
Get service
Read
Read service metadata and ownership IDs.
Permissions and limits
Account permissions
Read the selected service
Operation limits
Returns typed resource summaries. Embedded integrations, arbitrary catalog properties, alert email addresses and included resources are excluded.
Get team
Read
Verify one incident-response team by its exact ID without returning paging configuration.
Permissions and limits
Account permissions
Read the selected team
Operation limits
Returns typed resource summaries. Embedded integrations, arbitrary catalog properties, alert email addresses and included resources are excluded.
Link an existing Rootly incident to the ticket
Write
Link an existing Rootly incident to the run's ticket by its ID, or its number like #57. 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 incidents
Read
Find incident summaries by text and provider status.
Permissions and limits
Account permissions
Read accessible incidents
Operation limits
Returns one page with provider pagination metadata. Pass the next_page value as page. Page size is limited to 100 in NodeHub.
Returns typed resource summaries. Embedded integrations, arbitrary catalog properties, alert email addresses and included resources are excluded.
Pagination: page. Check the result for additional pages; a single action may not return every record.
List services
Read
Search the service catalog accessible to the selected account.
Permissions and limits
Account permissions
Read accessible services
Operation limits
Returns one page with provider pagination metadata. Pass the next_page value as page. Page size is limited to 100 in NodeHub.
Returns typed resource summaries. Embedded integrations, arbitrary catalog properties, alert email addresses and included resources are excluded.
Pagination: page. Check the result for additional pages; a single action may not return every record.
List severities
Read
Read the severities an incident can have, with their IDs.
Permissions and limits
Account permissions
Read severities
List teams
Read
Read one page of accessible incident-response teams.
Permissions and limits
Account permissions
Read accessible teams
Operation limits
Returns one page with provider pagination metadata. Pass the next_page value as page. Page size is limited to 100 in NodeHub.
Returns typed resource summaries. Embedded integrations, arbitrary catalog properties, alert email addresses and included resources are excluded.
Pagination: page. Check the result for additional pages; a single action may not return every record.
Update incident
Write
Update incident details, affected services or lifecycle status.
Permissions and limits
Account permissions
Update the selected incident
Operation limits
Rootly may run configured incident workflows and notify responders when incidents are created or updated.
Provided relationship ID arrays replace those incident associations. Omitted fields stay unchanged.
Returns typed resource summaries. Embedded integrations, arbitrary catalog properties, alert email addresses and included resources are excluded.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Update service
Write
Update a selected catalog service without modifying integration settings.
Permissions and limits
Account permissions
Update the selected service
Operation limits
Provided relationship ID arrays replace those service associations. An empty ownerTeamIds array removes all owner teams.
Returns typed resource summaries. Embedded integrations, arbitrary catalog properties, alert email addresses and included resources are excluded.
A repeated request may repeat the external action. Review the previous result before retrying a write.
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 Rootly. A saved workflow is not a completed provider action.
Alerting & Incidents · CONNECTION
