Agenty and Better Stack Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Keep Agenty and Better Stack matched by integrating their events and actions. When developer tools events happen in Agenty, update the Better Stack 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 Agenty and Better Stack
Detailed info you need to know about Agenty and Better Stack 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]
Better Stack

Uptime monitoring, incident management and status pages.[6]
How to connect Agenty to Better Stack
Set up your Agenty and Better Stack integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Agenty and Better Stack
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 Better Stack 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 Better Stack. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Agenty and Better Stack work in WEXTL?
WEXTL exposes actions and triggers for Agenty and Better Stack 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 triggersBetter Stack 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.
Better Stack modules
- Change the Incident Status Moves an incident to a new state: Action offers Acknowledge, Resolve and Reopen. Use By to record who made the change. The updated incident is returned.
- Change the Role of a Team Member Gives an existing team member a different Role, taken from your list of roles. Use Member to say whose role changes.
- Create a Catalog Attribute Gives a catalog relation another attribute under a Name. Turn on Primary to match it against the incident metadata key of the same name, and give a Position to order it, lowest first.
- Create a Catalog Record Stores one record in a catalog relation. Fill Attributes with one row per attribute, each row holding its values.
- Create a Catalog Relation Defines a catalog relation under a Name, with an optional Description. Set Match Rule to apply a record when any primary value or every primary value matches the incident metadata.
- Create a Heartbeat Sets up a heartbeat that expects a ping every Expected Every seconds and counts one as missed after the Grace Period. Choose an Escalation Policy to decide who is alerted, or alert the on-call person with the e-mail, SMS or Call switches.
- Create a Heartbeat Group Starts a group for heartbeats under a Name. Sort it among the other groups with Position, or begin with every heartbeat inside it paused by using Paused.
- Create a Monitor Starts a monitor that checks a chosen Monitor Type against a URL or Host. Use Check Frequency and Regions to set how often and where it runs, and Escalation Policy to decide who is alerted.
- Create a Monitor Group Sets up a home for monitors under a Name. Turn on Paused to pause every monitor in that group.
- Create a Severity Defines a severity level that decides how people are notified when an incident of that level opens. Pick channels with Send SMS, Call, Send E-mail, Send Push Notification and Send Critical Alert, and file it under a Severity Group.
- Create a Severity Group Adds a named group for severities, shown in the dashboard. Use Position to order it in the list, lowest first.
- Create a Status Page Creates a status page for your company from a Company Name, Time Zone and Subdomain, which must be unique across Better Stack. Add a Custom Domain, a Design, History Days or a Password to shape who sees what.
- Create a Status Page Group Creates a named group for status pages, shown in the dashboard. Use Position to place it in the list.
- Create a Status Page Report Publishes a report with a Title and the first status update Message. Choose a Report Type, either a manual incident or planned maintenance, and turn on Notify Subscribers to e-mail them.
- Create a Status Page Resource Adds an item to a status page based on its Resource Type, shown there under the Public Name. Use Mark as Down When and Mark as Degraded When to define how an incident affects it.
- Create a Status Page Section Sets up a section for grouping the items of a status page. Leave Name blank to hide its header, and use Position with Fixed Position to place it exactly.
- Create a Status Page Subscriber Subscribes an E-mail address to the updates of a status page.
- Create a Status Update Posts a follow-up on a status page report with the text from Message. Use Affected Resources for a manual report and leave it out for maintenance. Turn on Notify Subscribers to send an e-mail.
- Create an Escalation Policy Group Makes a group for escalation policies, shown in the dashboard under its Name. Use Position to place it in the list, lowest first.
- Create an Incident Opens an incident on behalf of a Requester E-mail, described by its Summary. Add a Name, a longer Description and an Escalation Policy, or alert the on-call person with Send E-mail, Send SMS or Call.
- Create an Incident Comment Posts a Comment on an incident, with Markdown supported. Set Tag Member to notify a colleague about it. The new comment is returned.
- Create an Incoming Webhook Creates a webhook endpoint that raises incidents from outside requests. Give it a Name and an Escalation Policy, and set Recovery Period for how long to wait after a resolving request. Start, Acknowledge and Resolve rules decide when each happens.
- Create an On-Call Event Puts people on call for a stretch of time on a schedule, between Starts At and Ends At. Everyone chosen as On-Call Users must belong to the schedule team. Turn on Override so the event beats regular scheduled ones.
- Create an On-Call Rotation Rotates On-Call Users through a schedule, each person on call for the Rotation Length counted in the chosen Interval. Rotations run from Start At to End At. Use Working Hours to restrict when anyone is paged.
- Create an On-Call Schedule Creates a new on-call schedule under a Name, which can then hold events and rotations.
- Delete a Catalog Attribute Deletes an attribute that belongs to a catalog relation.
- Delete a Catalog Record Removes a record that belongs to one catalog relation.
- Delete a Catalog Relation Deletes a catalog relation, the set of attributes and records matched against incident metadata.
- Delete a Heartbeat Removes a heartbeat that expects regular pings.
- Delete a Heartbeat Group Deletes a group that can pause and organise heartbeats together.
- Delete a Monitor Deletes a monitor that checks a website, server or port.
- Delete a Monitor Group Removes a group that holds monitors and can pause them together.
- Delete a Severity Removes a severity level used to decide how people are notified of new incidents.
- Delete a Severity Group Deletes a dashboard group that holds severity levels.
- Delete a Status Page Removes the status page on which visitors check the health of your services. Check first, it is final.
- Delete a Status Page Group Deletes a dashboard group that collects status pages.
- Delete a Status Page Report Removes a report, either an incident or planned maintenance, from a status page.
- Delete a Status Page Resource Deletes an item from a status page, found by Status Page and Resource.
- Delete a Status Page Section Removes a section that groups the items of a status page.
- Delete a Status Page Subscriber Unsubscribes an e-mail address from the updates of a status page.
- Delete a Status Update Deletes one update that was posted under a status page report.
- Delete an Escalation Policy Removes an escalation policy, the setting that decides who gets alerted.
- Delete an Escalation Policy Group Deletes a dashboard group used to organise escalation policies.
- Delete an Incident Removes an incident from your Better Stack account. Plan on it being final.
- Delete an Incident Comment Deletes a note that was posted in the thread of an incident.
- Delete an Incoming Webhook Removes an incoming webhook that raises incidents from outside requests.
- Delete an On-Call Event Deletes a single on-call shift that was added to a schedule.
- Delete an On-Call Rotation Removes the rotation configured on an on-call schedule.
- Delete an On-Call Schedule Deletes an on-call schedule that people can be placed on through events and rotations.
- Get a Catalog Attribute Reads an attribute of a catalog relation, including whether it is primary and where it is positioned.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Agenty and Better Stack 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 Better Stack.
References
List of sources used to gather information about the Agenty and Better Stack integration.
- Agenty and Better Stack integration source code, module specs and credentials implementation.
- Our Agenty and Better Stack integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Agenty and Better Stack, 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
- Better Stack integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Agenty and Better Stack integration page documentation. Used sources, the role of AI, and how the team validates the result.