Connect Rootly integrations
VerifiedIncident management and on-call platform for detecting, responding to, and learning from incidents, connected to WEXTL workflows and AI agents. Send Rootly deploys, issues and webhook events into your engineering workflows. When Watch Events (Instant) fires, update the docs, notify a team or continue with Get a Cause.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Rootly integration
Triggers can detect changes in Rootly and run actions that can create, search or modify data inside Rootly automatically[3], exactly how you set them.
- Watch Events (Instant) Starts a workflow as soon as Rootly sends a webhook event, the moment it happens.
- Get a Cause Looks up a cause with its Slug, Public Name and Position.
- Get a Functionality Reads a functionality and its Notify Emails, Slug and Managed By.
- Get a Heartbeat Shows a heartbeat monitor with its Interval, Interval Unit and Alert Summary.
- Get a Pulse Reads a pulse by its Pulse ID, with its Source, Summary, Labels and External Url.
- Get a Retrospective Opens a retrospective by Retrospective ID, showing the Title and Status it has, along with its Resolved At time.
- Get a Schedule Loads a schedule with its Time Zone, Slack Channel and Owner Group IDs.
- Get a Service Reads a service with its Slug, Notify Emails and Managed By values.
- Get a Severity Looks up a severity with its Severity ranking, Color and Position.
- Get a Status Fetches an incident status by Status ID, with its Slug, Color and whether it is Enabled.
- Get a Status Page Displays a status page with its Slug, Public Title, Header Color and Footer Color.
- Get a Status Page Announcement Fetches an announcement by Announcement ID, showing the Title and Body it carries, along with its Published At time.
- Get a Status Page Event Looks up a status page event by its Status Page Event ID, showing its Status, Started At and Should Tweet setting.
- Get a Sub-Status Reads a sub-status with its Parent Status, Position and the dates it was created and updated.
- Get a Team Opens a team showing its Slug, Notify Emails and Managed By values.
- Get a User Retrieves a user with their Email, Full Name With Team and Time Zone.
- Get a Workflow Retrieves a workflow with its Command, Wait and Repeat Every Duration.
- Get an Action Item Fetches one action item by its Action Item ID, with its Summary, Kind, Priority and Status.
- Get an Alert Opens an alert and shows its Short ID, Source, Status and Summary.
- Get an Alert Event Looks up one alert event by Alert Event ID, with its Kind, Action and Notification Type.
- Get an Alert Urgency Reads an urgency level, including its Retrigger Timeout Minutes and Color.
- Get an Environment Reads an environment with its Slug, Managed By and External ID.
- Get an Escalation Policy Fetches a policy with its Repeat Count, Group IDs and Service IDs.
- Get an Incident Retrieves an incident with its Sequential ID, Title and Kind. Use Include to load related records, which are returned as Included.
- Get an Incident Role Returns a role with its Summary, Position, Optional and Enabled settings.
- Get an Incident Timeline Event Reads one timeline event by its Timeline Event ID, with its Event text, Visibility setting and Occurred At time.
- Get an Incident Type Reads an incident type with its Slug, Color and Public Name.
- Get an Override Shift Fetches an override by Override Shift ID, with its Starts At, Ends At and Schedule ID.
- Get the Current User Returns the Rootly user behind the credential, with Email, Full Name and Time Zone.
- List Action Items Pulls action items across incidents. Filter on Kind, Priority, Status or Incident Status, and bound the deadline with Due From and Due To.
- List Action Items of an Incident Returns the follow-up tasks that belong to a single incident, one result per task.
- List Alert Events Returns the events logged on alerts. Filter by Kind or Alert ID, bound them with Created From and Created To, and order them with Sort.
- List Alert Sources Finds the sources that send you alerts, optionally matching Search or Name, or keeping only Enabled ones.
- List Alert Urgencies Browses urgency levels. Set Search or Name to match one and Sort to order the result.
- List Alerts Retrieves alerts. Filter on Status, Source, Services, Environments, Teams or Labels, with optional time windows.
- List Alerts of an Incident Returns the alerts linked to one incident, as separate results.
- List Causes Lists causes, matched by text through Search or Name.
- List Environments Collects the environments of your catalog. Look one up through Search or Name, filter on Color, and arrange the result with Sort.
- List Escalation Policies Returns escalation policies matching a Search, Name or Teams value.
- List Events of an Alert Shows the feed of one alert, filtered through Kind or Action.
- List Functionalities Gets functionalities from your catalog. Provide Search, Name or External ID to find some, and Sort to arrange them.
- List Heartbeats Lists heartbeat monitors, matched by text through Search or Name.
- List Incident Roles Lists the roles available to responders. Turn on Enabled for active roles only, and add Search, Name or Sort to refine the result.
- List Incident Timeline Events Reads the timeline of one incident entry by entry, in a single request.
- List Incident Types Lists incident types, matched through Name and ordered with Sort.
- List Incidents Retrieves incidents. Filter on Status, Kind, Severity, Services, Teams or Environments, and bound them with Created From or Updated From.
- List On-Calls Shows who is on call right now, or within a window from Since to Until. Turn on First Entry Only to keep one entry per escalation level.
- List Override Shifts Lists the temporary on-call covers placed on a schedule.
- List Pulses Reads pulses from a Source, for chosen Services, Environments or Labels, within Started From and Started To.
- List Retrospectives Finds retrospectives by Search text, Status, Severity or Incident ID, within date windows such as Created From and Resolved From.
- List Schedules Lists on-call schedules matching a Search, Name or Teams value.
- List Services Browses the service catalog, with Search, Name, External ID and Backstage ID to locate services and Sort to arrange them.
- List Severities Reads the severity levels you defined. Add Search, Name, Severity Level, Color or Sort to refine the result.
- List Shifts Reads shifts across schedules between From and To. Restrict them to some Schedules or Users.
- List Shifts of a Schedule Shows the shifts of one schedule, optionally limited to a range between From and To.
- List Status Page Announcements Returns the announcements posted to one status page, each with its Title and Body.
- List Status Page Events of an Incident Returns the updates posted to status pages for one incident, such as investigating or resolved notices.
- List Status Pages Browses status pages, optionally refined by Search, Name and Sort.
- List Statuses Lists incident statuses, with Slug and Name to locate one and Enabled to keep only active statuses.
- List Sub-Statuses Lists sub-statuses. Restrict them to one Parent Status, and match text with Slug or Name.
- List Teams Finds teams, with Search, Name, External ID and Color to narrow the result and Sort to arrange it.
- List Users Looks through the people in your account by Email, Search text, Role ID or On-Call Role ID, then orders them with Sort.
- List Workflow Runs Reads the runs of one workflow between Created From and Created To.
- List Workflows Browses workflows. Add Search or Name to match one, and Sort for the order.
- Acknowledge an Alert Marks an alert as acknowledged. Use Actor Email to record a specific user as the one who did it, when your organization has actor attribution turned on.
- Add a Note to an Alert Writes a Note on the activity feed of an alert, credited to the chosen User.
- Add a Timeline Event to an Incident Writes an Event on the timeline of an incident. Set Visibility to control who can read it.
- Add Subscribers to an Incident Subscribes the chosen Users to updates on an incident. Turn on Skip Users Without Access to a Private Incident to leave out anyone who cannot see it.
- Assign a Role to a User on an Incident Gives a user an Incident Role on a single incident and returns the updated incident.
- Attach Alerts to an Incident Links existing alerts to an incident by their Alert IDs and returns the Incident ID with its Alerts.
- Cancel an Incident Cancels an incident, with an optional Cancellation Message giving the reason.
- Create a Cause Adds a cause that incidents and retrospectives can be traced to. Give it a Name, and a Public Name and Public Description for status pages.
- Create a Functionality Adds a functionality, a capability of your product, from its Name. Link Owner Teams, Owner Users, Environments and Services to show who is behind it.
- Create a Heartbeat Sets up a heartbeat that alerts when pings stop. Define the Interval with its Interval Unit, an Alert Summary, and who to page through Notification Target Type and Notification Target ID.
- Create a Pulse Records a pulse from its Summary. Link Services and Environments, and use Labels, References and Data for extra detail.
- Create a Schedule Creates an on-call schedule from a Name and an Owner. Use Time Zone, Owner Teams and Send Shift Reports to adjust it.
- Create a Service Registers a service from its Name. Link Owner Teams, Owner Users, Related Services and an Alert Urgency to place it in the rest of your setup.
- Create a Severity Adds a severity level from a Name. Use Severity Level to rank how serious it is, and Color and Notify Emails to customise it.
- Create a Status Page Builds a status page titled by Title. Turn Public and Enabled on or off, style it with Header Color and Footer Color, and choose Services and Functionalities to cover.
- Create a Status Page Announcement Posts an announcement to a status page, from its Title and Body. Turn on Notify Subscribers to alert followers.
- Create a Sub-Status Adds a sub-status under a Parent Status, from a Name. Use Position to order it among its siblings.
- Create a Team Forms a responder team called Name. Add Members and Admins, a Color and an Alert Urgency, and switch on Alerts by Email.
- Create an Action Item Adds a follow-up task to an incident from its Summary. Set a Kind, Priority and Due Date, and name an Assignee or Assigned Teams to own it.
- Create an Alert Raises an alert from a Summary. Link Services, Teams and Environments, choose an Alert Urgency, and page someone with Notification Target Type and Notification Target ID.
- Create an Alert Urgency Defines an urgency level from a Name and Description. Use Retrigger After to set how long Rootly waits before alerting again on an unacknowledged alert.
- Create an Environment Adds an environment such as production, from its Name. Use Notify Emails, Color and External ID to describe and link it.
- Create an Escalation Policy Builds an escalation policy from a Name. Use Repeat Count to loop it several times, and Teams and Services to attach it.
- Create an Incident Declares an incident. Add a Title, Severity and Summary, link Services, Environments and Incident Types, and set Private to restrict who can see it.
- Create an Incident Role Defines a role people can hold during incidents, from a Name. Turn on Optional, Enabled or Allow Several Users to shape it.
- Create an Incident Type Adds a type for classifying incidents, from a Name. Use Color and Notify Emails to customise it.
- Create an Override Shift Puts a User on call for a window on a schedule, between Starts At and Ends At in UTC.
- Delete a Cause Deletes a cause used to classify incidents.
- Delete a Functionality Removes a functionality, a product capability, from the catalog.
- Delete a Heartbeat Deletes a heartbeat monitor that expected regular pings.
- Delete a Schedule Removes an on-call schedule from Rootly.
- Delete a Service Deletes the chosen service from the Rootly account.
- Delete a Severity Removes a severity level used for incidents.
- Delete a Status Page Deletes a customer-facing status page from Rootly.
- Delete a Status Page Announcement Removes an announcement posted on a status page.
- Delete a Status Page Event Deletes an incident update that was posted to a status page.
- Delete a Sub-Status Deletes a sub-status that sits under a parent status.
- Delete a Team Removes a team from Rootly once Confirm is turned on, because it cannot be undone.
- Delete an Action Item Deletes an action item from Rootly. Turn on Confirm to go ahead, because it cannot be undone.
- Delete an Alert Urgency Removes an urgency level that alerts can carry.
- Delete an Environment Removes an environment from your Rootly catalog.
- Delete an Escalation Policy Deletes a paging policy from Rootly.
- Delete an Incident Removes an incident and its record from Rootly.
- Delete an Incident Role Removes a role that responders can take during incidents.
- Delete an Incident Timeline Event Deletes one chronology entry from the timeline of an incident.
- Delete an Incident Type Removes a type used to classify incidents.
- Delete an Override Shift Deletes a temporary on-call override from a schedule.
- Detach an Incident from Its Parent Separates a child incident from the parent incident it was grouped under.
- Escalate an Alert Raises an alert to a higher level of an escalation policy. Name the Escalation Policy and Escalation Policy Level, or leave the level empty for the next one.
- Make an API Call Calls the Rootly REST API directly with a free-form request under your saved credential.
- Mark an Incident as Mitigated Moves an incident to mitigated. Add a Mitigation Message to say what was done.
- Move an Incident to Triage Moves an incident into the triage state and shows its Summary and Title.
- Ping a Heartbeat Sends a ping to a heartbeat to show the monitored job is still running.
- Post a Status Page Event for an Incident Posts a notice about an incident to a status page, from its Event text. Use Notify Subscribers or Post to Twitter to spread it.
- Remove a Role from a User on an Incident Withdraws an Incident Role from a user on one incident. Use Confirm to proceed.
- Remove Subscribers from an Incident Unsubscribes the chosen Users from an incident. Use Skip Users Without Access to a Private Incident to leave out those who cannot see it, and Confirm to proceed.
- Resolve an Alert Closes an alert as resolved. Add a Resolution Message, and set Resolve Related Incidents to close linked incidents too.
- Resolve an Incident Marks an incident as resolved. Add a Resolution Message to record the outcome.
- Restart an Incident Reopens an incident so it is active again, returning its Title and Kind.
- Run a Workflow Starts a workflow on an incident, retrospective, action item or alert. Turn on Check Conditions to skip the run when its conditions are not met, and add Context as a JSON object.
- Snooze an Alert Silences an alert for as many minutes as Delay (Minutes) says.
- Update a Cause Revises a cause: Name, Description, Public Name or Position.
- Update a Functionality Rewrites a functionality: Name, Description, Color or Notify Emails, and who owns it through Owner Teams and Owner Users.
- Update a Heartbeat Retunes a heartbeat: Name, Interval with Interval Unit, Alert Summary or Enabled. Use Clear Fields to empty values.
- Update a Pulse Amends a pulse: Summary, Source, Started At or Ended At, with optional Labels, References and Data.
- Update a Retrospective Rewrites a retrospective: Title, Content, Status, or timing through Started At, Mitigated At and Resolved At. Relink Causes as needed.
- Update a Schedule Updates a schedule: Name, Owner, Time Zone or Description. Switch All-Time Coverage, Notify When a Shift Starts or Send Shift Reports.
- Update a Service Changes a service: Name, Description, Color or Notify Emails, plus links through Owner Teams, Owner Users and Related Services.
- Update a Severity Tunes a severity: Name, Severity Level, Color or Position.
- Update a Status Page Reworks a status page: Title, Public Title, Header Color or Footer Color. Turn Public and Enabled on or off, and choose Services and Functionalities.
- Update a Status Page Announcement Replaces the Title or Body of an announcement already posted to a status page.
- Update a Status Page Event Rewrites the Event text or Status of a status page update. Turn on Notify Subscribers or Post to Twitter to spread the change.
- Update a Sub-Status Reshapes a sub-status: Name, Description or Position.
- Update a Team Modifies a team: Name, Description or Color, and who belongs through Members and Admins. Switch Alerts by Email on or off as needed.
- Update a User Changes a user: First Name, Last Name, Role ID or On-Call Role ID.
- Update a Workflow Adjusts a workflow: Name, Description, Position or Enabled.
- Update an Action Item Edits an action item: Summary, Description, Kind, Priority, Status or Due Date. Reassign it to an Assignee or Assigned Teams, and use Clear Fields to empty values.
- Update an Alert Changes an alert: Summary, Description, Source or Noise. Relink Services, Teams or Environments as needed.
- Update an Alert Urgency Adjusts an urgency level: Name, Description, Position or Retrigger After.
- Update an Environment Modifies an environment: Name, Color, Notify Emails or External ID.
- Update an Escalation Policy Alters a policy through its Name, Description or Repeat Count, plus the Teams and Services it applies to.
- Update an Incident Updates an incident: Title, Severity, Summary, Kind or Status. Relink Services, Functionalities or Environments, and use Clear Fields to empty values.
- Update an Incident Role Adjusts a role: Name, Summary, Description or Position. Switch Optional, Enabled or Allow Several Users on or off.
- Update an Incident Timeline Event Rewrites the Event text of a timeline entry, or changes its Visibility.
- Update an Incident Type Revises an incident type: Name, Description, Color or Public Name.
- Update an Override Shift Changes who covers an existing override by setting a different User. The user is the only thing Rootly lets you change.
How to integrate Rootly in automation workflow?
Rootly in three steps: start with "Watch Events (Instant)", connect one credential, then add your next step.
STEP 1
Select Rootly in workflow
Add the "Watch Events (Instant)" trigger from Rootly to the canvas[4].
STEP 2
Connect Rootly
Pick one of the 2 Rootly credential types and set it up once. All 149 Rootly modules use it[3].
STEP 3
Build a workflow
Add "Get a Cause" or "Get a Functionality" after it, then connect any app[5] or the HTTP node.
How Rootly connects and integrates with WEXTL
Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever Rootly app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that Rootly supports.
Full Rootly API documentationThe following table illustrates what fields Rootly integration require during authorization flow inside our workflow builder[4].
Connect Rootly
API Key*Text
••••••••
| Field | Type | Help |
|---|---|---|
API KeyRequired | password | In Rootly open Organization Settings, then API Keys, then Generate New API Key. Use a Global or Team key for automation. A Personal key stops working when its owner leaves. Copy it right away, it is shown once. |
Connect Rootly to popular apps on WEXTL
Enter a name of the other app you want to sync with Rootly below. Click on selected app to explore integration options with Rootly. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.
Example automation with Rootly integration
Select Watch Events (Instant) trigger from Rootly - this will be a starting point in your automation. Whenever event happens in Rootly, workflow will start[7] from Watch Events (Instant) node.
Search for Add a Timeline Event to an Incident, connect it as the next step of integration sequence. You can use filters between Watch Events (Instant) and Add a Timeline Event to an Incident, so only important data pass from Watch Events (Instant) to the next step. WEXTL gives you full control over the process of Rootly automation. All parts of workflow are visible on the canvas[4].
Rootly on WEXTL has 150 modules for creating developer tools automations. Explore Rootly documentation for more.
- RootlyWatch Events (Instant)
- Vectorizer AIPerforms action
OR
- Vectorizer AITriggers
- RootlyAdd a Timeline Event to an Incident
Frequently asked questions
Common questions about automating Rootly in your workflows.
What triggers does Rootly support?
Rootly has 1 trigger, including "Watch Events (Instant)". Triggers are start points of the workflow, and automations may start from them.
What actions can I run in Rootly?
Integration has 149 actions, including "Get a Cause", "Get a Functionality", and "Get a Heartbeat", and more. Refer to our Rootly Documentation for detailed inputs and outputs.
Do I need to write code to build automations?
No. The 149 Rootly modules, like "Get a Cause", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].
Is the integration secure?
Yes. Rootly has 2 credential types (1 sign-in, 1 you fill in), and each module uses the one it needs. WEXTL encrypts them at rest, and only your team can use them.
How does WEXTL integrate with Rootly?
Through the official Rootly API: 149 modules, plus "Make an API Call" for any endpoint they don't cover[3].
Can I use webhooks with Rootly?
Yes. "Watch Events (Instant)" is instant: Rootly pushes each event, so there is no polling delay.
Why use WEXTL platform for Rootly automation?
WEXTL is an AI-first visual canvas: describe the Rootly flow in plain words and AI wires the nodes[4].
References
List of sources used to gather information about the Rootly integration.
- Rootly integration source code, module specs and credentials implementation.
- Internal Rootly integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Rootly vendor API documentation, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® Rootly App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation
How we write and maintain Rootly app documentation
Explore how WEXTL® crafted Rootly integration page documentation. Used sources, the role of AI, and how the team validates the result.





















