Agenty and Pingdom Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect Agenty and Pingdom to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Agenty and Pingdom

Detailed info you need to know about Agenty and Pingdom integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Agenty

    • Developer Tools
    • 1 trigger
    • 28 searches
    • 43 actions

    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]

  • Pingdom

    • Developer Tools
    • 2 triggers
    • 29 searches
    • 22 actions

    Website and server monitoring with uptime checks, alert contacts, maintenance windows and outage reports.[6]

How to connect Agenty to Pingdom

Set up your Agenty and Pingdom integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Agenty and Pingdom work in WEXTL?

WEXTL exposes actions and triggers for Agenty and Pingdom 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 triggersPingdom 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.

Pingdom modules

  • Create a Check Starts monitoring a Host with a chosen Check Type and Name. Add Check Interval (Minutes), Probe Regions or Response Time Threshold (ms) to tune the runs, and Contacts To Alert or Teams To Alert to notify people.
  • Create a Maintenance Window Plans a quiet period with a Description, Start and End, during which chosen Uptime Checks or Transaction Checks are not alerted. Repeat, Repeat Every and Repeat Until make it recur.
  • Create a Transaction Check Sets up a scripted browser check from a Name and the Steps to run. Add Region, Interval (Minutes) and Alert After Failed Tests to decide where, how often and when it alerts.
  • Create an Alerting Contact Adds a person to notify about check problems. Add Email Targets and SMS Targets for where alerts reach them, or turn on Paused to hold notifications.
  • Create an Alerting Team Groups people into a team under a Name, built from a list of Members.
  • Delete a Check Deletes an uptime check along with all data collected for it. This cannot be undone.
  • Delete a Maintenance Occurrence Removes one scheduled slot that belongs to a maintenance window.
  • Delete a Maintenance Window Cancels planned downtime by deleting a maintenance window from the account.
  • Delete a Transaction Check Deletes a scripted transaction check from the account.
  • Delete an Alerting Contact Deletes a person who is notified about check problems.
  • Delete an Alerting Team Removes a group of alert recipients from the account.
  • Delete Multiple Checks Removes a batch of uptime checks with one request.
  • Delete Multiple Maintenance Occurrences Deletes a batch of downtime slots with a single request.
  • Delete Multiple Maintenance Windows Removes several maintenance windows at once.
  • Get a Check Reads an uptime check with its Hostname, Status and Resolution. Turn on Include Teams to add the alerting teams.
  • Get a Maintenance Occurrence Reads one occurrence of a maintenance window, showing its start (From) and end (To).
  • Get a Maintenance Window Shows a maintenance window with its Description, Recurrencetype and Repeatevery.
  • Get a Performance Summary Reads the response times of a check, one entry per interval of the chosen Resolution. Turn on Include Uptime to add uptime and downtime to each interval.
  • Get a Root Cause Analysis Reads one root cause analysis of an outage for a check. Analysis IDs come from List Root Cause Analyses.
  • Get a Transaction Check Fetches a transaction check with its Active flag, Interval and timestamps. Turn on Include Extended Tags for tag details.
  • Get a Transaction Check Status Report Shows the States of a transaction check for the period from From to To, sorted by Order.
  • Get a Transaction Performance Report Reads response Intervals of a transaction check over time. Use Resolution to pick the interval size and Include Uptime to add availability.
  • Get an Alerting Contact Reads a notification contact with its Type, Owner and Notification Targets.
  • Get an Alerting Team Reads a notification team and shows all of its Members.
  • Get an Average Summary Averages the Responsetime and Status of a check over From to To. Use By Country or By Probe to group the result, and Include Uptime to add the uptime totals.
  • Get an Hours Of Day Summary Shows the average response for each Hour of the day for a check. Turn on Use Local Time to group by the time zone of the account instead of UTC.
  • Get an Outage Summary Lists the up and down periods (States) of a check from From to To. Use Order to start from the newest or the oldest.
  • Get the Credits Shows the credit limits of the account, such as Checklimit, Availablechecks and Availablesms.
  • Get the Reference Data Shows lookup lists of Regions, Timezones, Countries and Phonecodes.
  • List Alerting Contacts Gives every notification contact with its Paused flag, Type and Notification Targets.
  • List Alerting Teams Lists every notification team with their Members to see who belongs where.
  • List Alerts Retrieves alerts that were sent, filtered by Check IDs, Contact IDs, Status or Sent Via, within From and To.
  • List Check Results Pulls raw test results of a check, each with Probeid, Status and Responsetime. Filter by Probe IDs or response time bounds.
  • List Checks Reads uptime checks with their Lasttesttime and Lastresponsetime. Use Tags to keep only checks with those tags.
  • List Maintenance Occurrences Retrieves occurrences of maintenance windows from From to To, with Maintenance Window to focus on one.
  • List Maintenance Windows Lists maintenance windows with their Description, Recurrencetype and Repeatevery. Use Order By to pick the sort field and Order to set the direction.
  • List Probes Finds the testing locations with Country, City and Hostname. Turn on Only Active or Include Deleted to filter.
  • List Probes Used By a Check Names the Probes that tested a check since From, up to To if given.
  • List Root Cause Analyses Reads the root cause analyses for outages of a check between From and To, each with its Timefirsttest and Timeconfirmtest.
  • List Transaction Checks Gets scripted checks with their Active flag and Interval, limited to some Tags or one Type.
  • List Transaction Status Reports Shows status reports of transaction checks with their States. Turn on Omit Empty to drop checks without data.
  • Make an API Call Sends a free-form request to the Pingdom REST API, signed with your saved credential.
  • Run a Single Test Runs one immediate test of a Host with a Check Type, from a Probe or Probe Regions. Set Path, Port or HTTP Authentication to aim the request.
  • Run a Traceroute Traces the network route to a Host, optionally from a given Probe.
  • Update a Check Edits a monitor, from its Host and Check Interval (Minutes) to its Probe Regions and Contacts To Alert.
  • Update a Maintenance Occurrence Moves one occurrence to a new Start and End.
  • Update a Maintenance Window Edits the Description, Start, End or repeat settings of a maintenance window. Use Clear Fields to blank chosen values.
  • Update a Transaction Check Edits a scripted check, covering its Steps, Region, Interval (Minutes) or Severity.
  • Update an Alerting Contact Changes the Name of a notification contact, its Email Targets and SMS Targets, or sets Paused.
  • Update an Alerting Team Renames a notification team or replaces its Members.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Agenty and Pingdom integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Agenty and Pingdom on WEXTL®

Claim your 3-day trial to build Agenty with Pingdom integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Agenty and Pingdom.

How do I connect Agenty and Pingdom?

Connect your Agenty and Pingdom accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Agenty and Pingdom?

Example: when the "Watch Agent Jobs" trigger in Agenty fires, WEXTL can "Create a Check" in Pingdom. Agenty has 1 trigger (including Watch Agent Jobs). Pingdom has 51 actions (including Create a Check, Create a Maintenance Window, and Create a Transaction Check). Add filters and transforms between steps when you need them.[1]

Can Agenty trigger actions in Pingdom, and Pingdom in Agenty?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Agenty and Pingdom?

No. Agenty-to-Pingdom automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Agenty integrate with Pingdom in real time?

Yes. Trigger-based automations start the moment Agenty (or Pingdom) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Agenty + Pingdom integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Agenty with Pingdom?

You can build your Agenty + Pingdom automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Agenty and Pingdom integration.

  1. Agenty and Pingdom integration source code, module specs and credentials implementation.
  2. Our Agenty and Pingdom integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Agenty and Pingdom, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Agenty integration information
  6. Pingdom integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Agenty and Pingdom integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Agenty and Pingdom, or get started