Apify and Pingdom Integration

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

Connect Apify 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 Apify and Pingdom

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

  • Apify

    • Developer Tools
    • 4 triggers
    • 55 searches
    • 60 actions

    Run Apify Actors and tasks, manage datasets and stores, and watch for Actor run completion events.[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 Apify to Pingdom

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

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

WEXTL exposes actions and triggers for Apify 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.

Apify triggersPingdom 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.

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 Apify and Pingdom integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Apify and Pingdom on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Apify and Pingdom.

How do I connect Apify and Pingdom?

Connect your Apify 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 Apify and Pingdom?

Example: when the "Watch Aborted Runs" trigger in Apify fires, WEXTL can "Create a Check" in Pingdom. Apify has 4 triggers (including Watch Aborted Runs, Watch Failed Runs, and Watch Succeeded Runs). 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 Apify trigger actions in Pingdom, and Pingdom in Apify?

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 Apify and Pingdom?

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

Does Apify integrate with Pingdom in real time?

Yes. Trigger-based automations start the moment Apify (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 Apify + 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 Apify with Pingdom?

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

References

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

  1. Apify and Pingdom integration source code, module specs and credentials implementation.
  2. Our Apify and Pingdom integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Apify 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. Apify 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 Apify and Pingdom integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Apify and Pingdom, or get started