Rootly

Rootly is incident management: teams declare incidents, run them to resolution, and keep a catalog of the services and teams those incidents hang off.

Authentication

• API key

Actions

Generic API request. Call any Rootly API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

• Get incidentRetrieve a single Rootly incident by id (GET /incidents/{incidentId}).
• List incidentsList the incidents recorded in the Rootly organization, for an incident review or to resolve an incident title to the id that timeline and action endpoints take.
• List servicesList the services registered in the Rootly organization, to resolve a service name to the id that incident impact and ownership fields take.
• List teamsList the teams defined in the Rootly organization, to resolve a team name to the id that incident ownership and notification rules take.

Triggers

• New incidentStarts when a new incident is declared in Rootly.
• New incidentStarts the moment a new incident is declared in Rootly, delivered by a webhook instead of polling the incident list.
• New serviceStarts when a new service is registered in the Rootly service catalog.
• New teamStarts when a new team is created in Rootly, such as when standing up a fresh on-call group.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.