Apify and Rootly Integration
Keep Apify and Rootly matched by integrating their events and actions. When developer tools events happen in Apify, update the Rootly 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 Apify and Rootly
Detailed info you need to know about Apify and Rootly integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Apify to Rootly
Set up your Apify and Rootly integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Apify and Rootly
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 Apify and Rootly 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 Apify and Rootly. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Apify and Rootly work in WEXTL?
WEXTL exposes actions and triggers for Apify and Rootly 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.
Apify triggersRootly actions
Apify modules
- Abort a Build Aborts a build while it is still running and ends its work early.
- Abort a Build (Cross-Actor) Ends a build directly through its Build, without first naming the Actor that owns it.
- Abort a Run Cancels a run that has not finished yet and halts whatever the Actor was doing.
- Abort a Run (Cross-Actor) Terminates a run directly through its Run, with no Actor needed.
- Add a Request to a Queue Puts a single new request into a request queue, where it waits to be processed.
- Batch Add Requests Adds up to 25 requests to a request queue in one call, each with a Unique key, URL, Method and Payload. Turn on Add to the front to place them at the head of the queue.
- Build an Actor Kicks off a new build for an Actor, producing a build record with a Status and Data.
- Charge Events in a Run Applies charges for events to an Actor run, identified by its Actor and Run.
- Create a Dataset Sets up a dataset in Apify storage and returns its Created at time.
- Create a Key-Value Store Opens a new key-value store, a place that keeps records under keys.
- Create a Request Queue Opens a new request queue that holds requests waiting to be processed.
- Create a Schedule Registers a schedule through Apify and returns its Name.
- Create a Task Saves a task with Apify and returns its Updated at time.
- Create a Version Attaches another version to an Actor, alongside the ones it already has.
- Create an Actor Creates an Actor in Apify and returns its ID and Name.
- Create an Environment Variable Defines a new environment variable on a particular Version of an Actor.
- Decode and Verify Data Decodes an encoded value and verifies it, the reverse of Encode and Sign Data.
- Delete a Dataset Removes a dataset from your Apify storage.
- Delete a Key-Value Store Deletes a key-value store held in your Apify storage.
- Delete a Record Removes the record kept under a given Recordkey in a key-value store.
- Delete a Request Removes the request with a given Requestid from a request queue.
- Delete a Request Queue Deletes a request queue from your Apify storage.
- Delete a Schedule Removes a schedule that exists in your Apify account.
- Delete a Task Deletes a stored task from your account.
- Delete a Version Removes a version that was attached to an Actor.
- Delete a Webhook Deletes a webhook configured on your Apify account.
- Delete an Actor Deletes an Actor from your Apify account.
- Delete an Environment Variable Removes an environment variable from the chosen Actor Version.
- Download Records (Batch Export) Downloads every record kept in a key-value store as one batch export.
- Encode and Sign Data Encodes and signs data, producing a value that Decode and Verify Data can check.
- Get a Build Reads a build of an Actor and reports its Status and last update.
- Get a Build (Cross-Actor) Reads a build straight from its Build, even when the owning Actor is not known.
- Get a Build Log Returns the log text that was produced while a build ran.
- Get a Build Log (Cross-Actor) Returns the log text of a build addressed by Build alone, whichever Actor it belongs to.
- Get a Dataset Reads the details of a dataset, including its Name and creation time.
- Get a Key-Value Store Reads the details of a key-value store such as its Name and timestamps.
- Get a Record by Key Reads the record kept under a given Recordkey in a key-value store.
- Get a Request Reads a single request from a request queue by its Requestid, including its Status and Data.
- Get a Request Queue Returns a request queue with its Name and creation time.
- Get a Run Fetches a single Actor run together with its Status and Updated at.
- Get a Run (by ID, Cross-Actor) Reads a run straight from its Run, regardless of the Actor behind it.
- Get a Schedule Returns a schedule with its Name, Status and Created at.
- Get a Schedule Log Returns the log describing what a schedule has done so far.
- Get a Task Reads the stored configuration of a task, along with its timestamps.
- Get a Task Input Reads the input values that are stored with a task and used when it runs.
- Get a Version Reads a version of an Actor together with its Name and timestamps.
- Get a Webhook Returns a webhook configuration with its Name and timestamps.
- Get a Webhook Dispatch Reads a single webhook dispatch by its Dispatchid, including its Status.
- Get an Actor Looks up an Actor and returns its ID, Name, Status and Data.
- Get an Environment Variable Reads a single environment variable defined for an Actor Version, with its Name.
Rootly modules
- 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.
- Get a Cause Looks up a cause with its Slug, Public Name and Position.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Apify and Rootly integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Apify and Rootly.
References
List of sources used to gather information about the Apify and Rootly integration.
- Apify and Rootly integration source code, module specs and credentials implementation.
- Our Apify and Rootly integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Apify and Rootly, 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.
- Apify integration information
- Rootly integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Apify and Rootly integration page documentation. Used sources, the role of AI, and how the team validates the result.

