Agenty and Rootly Integration
Build developer tools workflows between Agenty and Rootly on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Agenty and Rootly
Detailed info you need to know about Agenty and Rootly integrations in WEXTL. Explore which modules apps support and how you connect them.
Agenty

Cloud web scraping, crawling and change detection. Create and run scraping, crawling and monitoring agents, feed them URLs or stored lists, start jobs on demand or on a schedule, pull the extracted rows and logs, and react when a job completes.[5]
Rootly

Incident management and on-call platform for detecting, responding to, and learning from incidents.[6]
How to connect Agenty to Rootly
Set up your Agenty and Rootly integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Agenty 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 Agenty 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 Agenty and Rootly. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Agenty and Rootly work in WEXTL?
WEXTL exposes actions and triggers for Agenty 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.
Agenty triggersRootly actions
Agenty modules
- Watch Agent Jobs Starts the workflow instantly through a webhook, as soon as an agent job finishes or fails.
- Add Agents to a Project Files existing agents under an Agenty project. Use Agents to list which ones to include.
- Add Rows to a List Adds rows to a stored list. Use Rows for free-form row objects, which are sent as the entire request body.
- Cancel a Running Job Stops a job that is still running in Agenty. Use Agent to narrow the job choices to one agent.
- Change Agent Schedule Status Switches the run schedule of an agent on or off. Turn on Enabled to activate the schedule, or turn it off to pause it.
- Change API Key Status Changes the status of an Agenty API key by its numeric id from the API keys page. How the new status is chosen is undocumented and may toggle, so a retry may not be safe.
- Change Workflow Status Enables or disables an Agenty automation, which this app calls a workflow. Turn on Enabled to activate it, or turn it off to stop it from firing. Output returns Enabled.
- Copy an Agent Makes a duplicate of an existing agent. Add a Name to title the copy, bearing in mind the copy body is undocumented and the name goes out only if present.
- Create a List Creates a stored list. Give it a Name of up to 100 characters, and add a Description of up to 250 if useful. Output has the List ID.
- Create a Project Opens a new project for organizing agents. Add a Name to title it and a Description to explain it.
- Create a Workflow Sets up an Agenty automation, called a workflow here. It watches Agents for events chosen with Fire On, such as Job Failed or Change Detected, then runs its Actions. Use Enabled to start it on or off.
- Create an Agent Builds a new agent from a Name, a Type such as Scraping or Crawling, an Input to run against and a Config whose shape depends on the Type. Turn on Start after creation to run it straight away. Output gives the Agent ID.
- Create an API Key Generates a new API key in your Agenty account. Use Name as its display name, although the create body is undocumented and the name goes through only if present.
- Delete a Connection Removes a stored OAuth grant, and automations whose actions reference it will fail.
- Delete a List Deletes a stored list from Agenty. Removal is one-way.
- Delete a List Row Removes one row from a stored list, using the Row ID. The id is a string, even though list ids are numbers. The deletion sticks.
- Delete a Workflow Deletes an Agenty automation, which this app calls a workflow. Deleted items are lost.
- Delete Agents by Id Deletes several agents in a single call. Deleted data is lost.
- Delete an Agent Deletes one agent from your Agenty account. It stays removed.
- Delete an Agent Schedule Removes the run schedule that was set on an agent.
- Delete an API Key Deletes an Agenty API key. Nothing guards against deleting the very key this credential authenticates with. Deletion is one-way.
- Delete Projects by Id Deletes several projects in one call. It stays gone.
- Delete Rows by Id Removes several rows from a stored list at once. Fill Row IDs with their ids as one comma-separated string.
- Delete Users by Id Removes team members from your Agenty account. Deleted items stay gone.
- Download a Job Result Downloads the result of one job as a file. Use Collection to pick which output collection by number, Format for the file type, and Search to narrow the rows.
- Download API Keys as CSV Saves your API keys as a CSV file, narrowed with a Search text and arranged by Sort.
- Download Jobs as CSV Pulls job records into a CSV file, for every agent or for just one Agent. Order them with Sort.
- Download List Rows as CSV Writes every row of one stored list to a single CSV file.
- Get a Job Reads one agent job. Use Agent to narrow the job choices, then name the Job to read.
- Get a Job Output File Fetches one file produced by a job. Use File Name exactly as it appears in the job result.
- Get a Job Result Reads the rows a job produced. Use Collection to read a later collection than the first, Format for the result format, and Sort, Order or Search to shape the rows.
- Get a List Fetches a stored list record, giving its List ID, Name and Description.
- Get a List Row Fetches one row from a stored list. Give Row ID as a string here, since the row schema documents no stable id field.
- Get a Project Fetches the record of one Agenty project, to read its details.
- Get a User Looks up one team member, giving the User ID, Name, Email and Role.
- Get a Workflow Reads one automation with its Workflow ID, Name and the Agents it watches.
- Get an Account Usage Report Reads the usage dashboard of your Agenty account for a time window, running from Start to End, both inclusive.
- Get an Agent Fetches one agent, including its Agent ID, Project ID and Name.
- Get an Agent Input Shows what an agent is set to run against, as a Type and its Data.
- Get an Agent Schedule Reads the schedule attached to an agent, giving the next and the last run times as Next Scheduled Run At and Last Scheduled Run At.
- Get an API Key Looks up one API key by the numeric id shown on the API keys page in Agenty. There is no picker, because listing keys can expose secret material.
- Get Lists Browses your stored lists. Fill Search with free text to narrow them, and add Order to set the direction.
- Get the Latest Agent Result Reads the most recent result of an agent. Agenty requires Download on this read, to choose between inline rows and a file. Add Collection, Sort, Order or Search to narrow what is read.
- Invite a User Invites someone to join your Agenty team by Email. Use Role to grant owner, admin or manager access, and Name to add a display name.
- List Agents Shows the agents in your account, filtered by a Search text and ordered with Sort and Order.
- List API Keys Retrieves your Agenty API keys, optionally narrowed by a Search text.
- List Connections Lists the OAuth connections stored in your Agenty account.
- List Job Logs Reads the log lines of one job, narrowed by Search or arranged by Sort.
- List Jobs Finds agent jobs across every agent, or only those of one Agent. Add Order to choose the direction.
- List Projects Gives you the projects that group your agents, with an optional Search filter.
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 Agenty 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 Agenty and Rootly.
References
List of sources used to gather information about the Agenty and Rootly integration.
- Agenty and Rootly integration source code, module specs and credentials implementation.
- Our Agenty and Rootly integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Agenty 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.
- Agenty integration information
- Rootly integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Agenty and Rootly integration page documentation. Used sources, the role of AI, and how the team validates the result.