Connect Pingdom integrations
VerifiedWebsite and server monitoring with uptime checks, alert contacts, maintenance windows and outage reports, connected to WEXTL workflows and AI agents. Send Pingdom deploys, issues and webhook events into your engineering workflows. When Watch Alerts fires, update the docs, notify a team or continue with Get a Check.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Pingdom integration
Triggers can detect changes in Pingdom and run actions that can create, search or modify data inside Pingdom automatically[3], exactly how you set them.
- Watch Alerts Polls Pingdom for sent alerts, limited by Check IDs, Status or Sent Via, and triggers the workflow on each.
- Watch New Checks Looks every so often for checks added since the last run and fires the workflow once per check.
- 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.
- 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.
- 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.
- Make an API Call Sends a free-form request to the Pingdom REST API, signed with your saved credential.
- 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.
- Update Multiple Checks Changes several uptime checks in one call. Use Paused to pause or resume them and the interval field to set how often they run.
How to integrate Pingdom in automation workflow?
Pingdom in three steps: start with "Watch Alerts", connect one credential, then add your next step.
STEP 1
Select Pingdom in workflow
Add the "Watch Alerts" trigger from Pingdom to the canvas[4].
STEP 2
Connect Pingdom
Fill in the Pingdom credential once. All 52 Pingdom modules use it[3].
STEP 3
Build a workflow
Add "Get a Check" or "Get a Maintenance Occurrence" after it, then connect any app[5] or the HTTP node.
How Pingdom connects and integrates with WEXTL
Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever Pingdom app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that Pingdom supports.
Full Pingdom API documentationThe following table illustrates what fields Pingdom integration require during authorization flow inside our workflow builder[4].
Connect Pingdom
API Token*Text
••••••••
| Field | Type | Help |
|---|---|---|
API TokenRequired | password | In My Pingdom open Settings, API, and generate an API token. Use Read/Write access if workflows create or change anything. Read access is enough for reports. |
Connect Pingdom to popular apps on WEXTL
Enter a name of the other app you want to sync with Pingdom below. Click on selected app to explore integration options with Pingdom. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.
Example automation with Pingdom integration
Select Watch New Checks trigger from Pingdom - this will be a starting point in your automation. Whenever event happens in Pingdom, workflow will start[7] from Watch New Checks node.
Search for Create a Transaction Check, connect it as the next step of integration sequence. You can use filters between Watch New Checks and Create a Transaction Check, so only important data pass from Watch New Checks to the next step. WEXTL gives you full control over the process of Pingdom automation. All parts of workflow are visible on the canvas[4].
Pingdom on WEXTL has 53 modules for creating developer tools automations. Explore Pingdom documentation for more.
- PingdomWatch New Checks
- Straker AIPerforms action
OR
- Straker AITriggers
- PingdomCreate a Transaction Check
Frequently asked questions
Common questions about automating Pingdom in your workflows.
What triggers does Pingdom support?
Pingdom has 2 triggers, including "Watch Alerts" and "Watch New Checks". Triggers are start points of the workflow, and automations may start from them.
What actions can I run in Pingdom?
Integration has 51 actions, including "Get a Check", "Get a Maintenance Occurrence", and "Get a Maintenance Window", and more. Refer to our Pingdom Documentation for detailed inputs and outputs.
Do I need to write code to build automations?
No. The 52 Pingdom modules, like "Get a Check", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].
Is the integration secure?
Yes. You fill in the Pingdom credential once. WEXTL encrypts it at rest, and only your team can use it.
How does WEXTL integrate with Pingdom?
Through the official Pingdom API: 52 modules, plus "Make an API Call" for any endpoint they don't cover[3].
Can I use webhooks with Pingdom?
Pingdom doesn't push events here, so "Watch Alerts" and "Watch New Checks" check on the schedule you set. Anything Pingdom posts to a URL can start a Custom Webhook node.
Why use WEXTL platform for Pingdom automation?
WEXTL is an AI-first visual canvas: describe the Pingdom flow in plain words and AI wires the nodes[4].
References
List of sources used to gather information about the Pingdom integration.
- Pingdom integration source code, module specs and credentials implementation.
- Internal Pingdom integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Pingdom vendor API documentation, 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.
- WEXTL® Apps Library
- WEXTL® Pingdom App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation
How we write and maintain Pingdom app documentation
Explore how WEXTL® crafted Pingdom integration page documentation. Used sources, the role of AI, and how the team validates the result.





















