Rootly and Updown.io Integration
Keep Rootly and Updown.io matched by integrating their events and actions. When developer tools events happen in Rootly, update the Updown.io automatically - without any line of code in visual workflow builder.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Rootly and Updown.io
Detailed info you need to know about Rootly and Updown.io integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Rootly to Updown.io
Set up your Rootly and Updown.io integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Rootly and Updown.io
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected Rootly and Updown.io nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Rootly and Updown.io. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Rootly and Updown.io work in WEXTL?
WEXTL exposes actions and triggers for Rootly and Updown.io that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
Rootly triggersUpdown.io actions
Rootly modules
- Watch Events (Instant) Starts a workflow as soon as Rootly sends a webhook event, the moment it happens.
- 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.
Updown.io modules
- Create a Check Starts monitoring a URL or a heartbeat with updown.io. Use Period (Seconds) to set how often it runs and Apdex Threshold to set the response time that counts as satisfying.
- Create a Recipient Adds a place to send alerts, such as an email address, a phone number for SMS, or a webhook URL. Use Select on All Checks to attach it to every check you already have.
- Create a Status Page Builds a page that shows the state of several Checks, in the order given. Use Visibility and Access Key to control who can open it.
- Delete a Check Deletes one monitoring check from updown.io. This cannot be undone.
- Delete a Recipient Removes an alert recipient from your updown.io account. A webhook recipient may belong to a workflow trigger.
- Delete a Status Page Removes a published status page. This cannot be undone.
- Get a Check Reads one check with its URL, Uptime, Period and current Down state. Turn on Include Metrics for the last hour of performance figures, or Include Results for the last 5 requests.
- Get Check Metrics Reads Uptime, Apdex, Timings and Requests for one check over a period. Use From and To to set the window and Group By to split the totals.
- List Check Downtimes Finds each outage of one check with its Started At, Ended At and Duration (Seconds). Turn on Include Results to add the requests before the downtime and after recovery.
- List Checks Lists every check in your updown.io account with its Token, URL, Alias and Uptime. Use Limit to return fewer rows when you only need a few.
- List Node IP Addresses Lists the IP Address values that updown.io sends its checks from, for firewall allow lists. Use Address Family to get only IPv4 or only IPv6.
- List Nodes Shows the monitoring locations of updown.io with their Code, City and Country. Each row also has IPv4 and IPv6 values for that node.
- List Recipients Gets the alert recipients on your account, each with its ID, Type, Name and Value. Run it to find the ID of a recipient before removing one.
- List Status Pages Retrieves your status pages, each with its Token, Name and Visibility. Checks on every page are included.
- Make an API Call Calls the Updown.io REST API directly with a free-form request under your saved credential.
- Update a Check Edits the URL, Period (Seconds), Apdex Threshold or Enabled setting of an existing check. Alias, String Match and Mute Until change only when filled in.
- Update a Status Page Renames a status page or edits its Description, Visibility and Access Key. Use Checks to replace the whole list of checks it shows.
- Watch Events Starts the workflow the moment updown.io reports a check going down or coming back up. Use the Event, Time and Description values of each alert, plus the Check Alias and Check URL.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Rootly and Updown.io integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Rootly and Updown.io.
References
List of sources used to gather information about the Rootly and Updown.io integration.
- Rootly and Updown.io integration source code, module specs and credentials implementation.
- Our Rootly and Updown.io integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Rootly and Updown.io, 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.
- Rootly integration information
- Updown.io integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Rootly and Updown.io integration page documentation. Used sources, the role of AI, and how the team validates the result.

