Resources · Zapier integration

Pingdom Zapier integrationAutomate Pingdom with Zapier.

The Pingdom Zapier integration has 3 triggers, 1 action and 0 searches. The triggers watch new alerts, checks and contacts in your monitoring account; the action is an advanced request for edge cases. All 3 triggers are polling, so your plan sets how fast an alert travels.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What Zapier can do with your Pingdom account

Pingdom on Zapier mostly reads. It picks up new alerts, new checks and new contacts from your Pingdom account and hands them to the next steps of a Zap, in tools your team already uses. One advanced action can also send a raw request to Pingdom, for people comfortable with that.

Three results come up again and again. An outage relay: New Alert catches the alert for a chosen check and contact, then posts it where the on-call person actually looks. A monitoring log: New Check adds a line to a shared sheet each time someone sets up a new check, so nobody wonders who watches what. A contact roster: New Contact copies each new alert recipient into your team directory or ticket tool.

Now the honest part. All three triggers are polling: Zapier visits Pingdom on a timer, and on the free plan that means an alert can wait up to 15 minutes before your Zap even sees it. For outages, that delay matters, so weigh it before relying on this route. There is no search, and the only action is API Request (Beta), a raw request that asks you to know Pingdom's own address format. Zapier offers no simple action to pause a check or add a contact.

The same app also has a Pingdom Make integration page, useful if trigger speed decides your tool.

Vocabulary

Zapier vocabulary for Pingdom users

Eight words, one plain line each, as they apply to a Zap that starts in Pingdom.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event that starts a Zap, here a new alert, check or contact in Pingdom. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or moves something, often in another app such as a chat tool.
Task
The unit Zapier bills: one action your Zap completes successfully. Checking Pingdom for new items is free.
Polling trigger
A trigger Zapier checks on a timer, keeping only items it has not seen yet. All three Pingdom triggers work this way.
Instant trigger
A trigger the app reports itself, so nothing waits for the next check. Pingdom has none on Zapier.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
Cost

What a Pingdom Zap costs, and how fast it reacts

Zapier checking Pingdom costs nothing, however often it looks. Only actions that go through are billed.

  • Trigger cost0 tasks
  • Free plan100 tasks a month, 2 steps per Zap
  • Trigger type3 polling, 0 instant
  • Premium appNo, it works on Free

One alert relayed to chat is one task. A second action counts on its own, and a failed action is not billed against your plan. The free plan gives 100 tasks a month and unlimited Zaps, two steps per Zap, and checks Pingdom every 15 minutes. Paid plans check far more often, and the interval can be changed or a check run by hand from the editor. Adding a filter makes the Zap multi-step, so it needs a paid plan.

Connect

Connect Pingdom to Zapier in three steps

  1. 01

    Find Pingdom from the Apps page

    In your Zapier account, open the Apps page and click + Add connection. A dialog opens where apps are searched by name: type Pingdom and pick it from the results.

  2. 02

    Sign in to Pingdom

    Click Add connection and sign in to Pingdom in the tab that opens. Use the account that owns the checks you want to watch, or one with read access to them.

  3. 03

    Grant access

    Allow the access Zapier asks for. Every Zap and every step that uses Pingdom then reuses this connection, so a second monitoring Zap needs no fresh sign-in.

First Zap

Your first Pingdom Zap: outage alerts in your team chat

GoalEvery new Pingdom alert on your main website check that passes your rule becomes a message in the team's incident channel.

  1. 01

    Pick Pingdom and New Alert

    Start building with Pingdom as the app that starts the Zap and New Alert as the event, then select your Pingdom connection.

  2. 02

    Choose the check and the contact

    Pick the check you care about and the contact whose alerts count. Both are required. The Zap only reacts when that contact would be alerted for that check.

  3. 03

    Test on recent alerts

    Run the test. Zapier brings back the three most recent items of the connected account, so you map the message on a real alert, not on a made-up one.

  4. 04

    Add a filter

    Click the plus icon, choose Filter and fill the three boxes: the field to look at, the rule, the value. Use a text rule on text and a number rule on numbers. The Zap is now multi-step and needs a paid plan.

  5. 05

    Add the chat action

    Add the action in your chat app, choose the incident channel, and map the alert details you saw in the test into the message. Run the step once and read what came back.

  6. 06

    Publish

    Click Publish to switch the Zap on. On a paid plan Zapier checks Pingdom more often than the free plan's 15 minutes, which matters for outages.

Triggers

The 3 Pingdom triggers

3 events start a Zap when something happens in Pingdom. Zapier checks for them at the interval your plan allows.

1

New Check

Polling trigger

In Zapier“Triggers when a new check is added.”

Picks up each check added to your Pingdom account and starts a Zap with it. It keeps your other tools aware of what is now being monitored, without anyone keeping a list by hand.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
your agency adds a check for each new client site and wants a row in the shared client sheet.
Watch out
checks that already existed before the Zap was published are never sent, so list those separately.
2

New Contact

Polling trigger

In Zapier“Triggers when a new contact is added.”

Reacts when a contact is added in Pingdom, the people who receive alerts. Use it to keep a team directory or an on-call tool aligned with who Pingdom will actually warn.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a new engineer joins the rota and should also appear in your ticketing tool's contact list.
Watch out
Zapier keeps track of the contacts it has already seen, so the same contact never starts the Zap twice.
3

New Alert

Polling trigger

In Zapier“Triggers when a new alert occurs in Pingdom.”

The trigger most people come for. It hands each new Pingdom alert for one check to your Zap, so the outage reaches a channel, a ticket or a phone beyond the Pingdom inbox.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
your shop's checkout check fails and the incident channel should get a message with the details.
Watch out
you must choose a check and a contact, and the Zap only fires when that contact would be alerted.
Actions

The Pingdom action

Pingdom gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced step that sends a raw request to Pingdom with your connection already signed in. You pick the method and the address yourself, which covers moves Zapier has no ready-made action for.

When to use it
a technical teammate wants to reach a Pingdom feature that no simple action covers.
Watch out
the address must belong to Pingdom's own domains, and the required Stop on error choice decides whether a failure halts the Zap.
When it breaks

When a Pingdom Zap breaks

Zapier ties no help article to Pingdom and records no limit of its own for it. The breakdowns come from general Zapier rules, and on a monitoring tool they show up at the worst moment.

  • The alert arrives late

    All three triggers are polling. On the free plan Zapier looks every 15 minutes, so an outage can sit unseen for that long before the Zap runs.

  • Old alerts never show up

    A Zap only reacts to what happens after it is switched on. Alerts, checks and contacts from before stay in Pingdom; moving that history is a separate job.

  • The Zap keeps setting itself off

    If API Request (Beta) writes a check into the very account New Check watches, the Zap can set itself off again and again, burning through tasks.

  • A wave of alerts gets held back

    A big incident or a bulk import can return a huge batch at once. Zapier's flood protection can hold that batch back instead of running it.
Need help

Need help automating Pingdom with Zapier?

A person reads every message.

FAQ

Pingdom Zapier integration: frequent questions

01Is the Pingdom Zapier integration free?
Yes. Pingdom is not a premium app on Zapier, so it works on the free plan. That plan includes 100 tasks a month, unlimited Zaps and two steps per Zap, which fits a simple relay such as New Alert followed by one chat message. The catch is speed: on Free, Zapier checks Pingdom every 15 minutes. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan.
02How many tasks does a Pingdom Zap use?
Only the actions count. Zapier checking Pingdom for new alerts, checks or contacts costs nothing, however often it looks. Each action that completes successfully is one task, so an alert posted to chat and also logged in a sheet uses two tasks. A failed action is not billed. On a noisy check that alerts often, keep an eye on the monthly count against your plan before adding more actions to the Zap.
03Are Pingdom alerts sent to Zapier in real time?
No. All three Pingdom triggers are polling triggers: Zapier asks Pingdom for new items on a timer rather than being told right away. On the free plan that timer is 15 minutes, on Professional 2 minutes, on Team and Enterprise 1 minute. Paid plans can also change how often the check runs, and a check can be run by hand from the editor. For outage alerts, that interval is the number to look at first.
04What does it take to connect Pingdom to Zapier?
A Pingdom account and a Zapier account. On Zapier's Apps page, click + Add connection, search for Pingdom, click Add connection, sign in to Pingdom in the new tab and grant access. If the checks belong to a colleague, your account needs read access to them. For New Alert, have the check and its alert contact ready in Pingdom, since the trigger asks you to choose both. Sign in once, and every Pingdom Zap reuses that connection.
05Why does New Alert stay silent when a check fails?
Usually because of the contact setting. New Alert asks for a check and a contact, both required, and only passes alerts that this contact would receive. If the chosen contact is not on that check's alerts, the Zap never sees them. The second reason is timing: the trigger is polling, so on the free plan the alert can arrive up to 15 minutes later. Finally, alerts from before the Zap was published are never sent.
06What if the Pingdom action you need does not exist?
Zapier offers no ready-made Pingdom action beyond API Request (Beta), and no search. So pausing a check, adding a contact or editing a check have no simple step. API Request (Beta) may cover them if someone on the team can build a raw request to Pingdom's own domains, choosing the method and the address. If nobody can, handle those changes in Pingdom directly and keep Zapier for relaying what Pingdom reports.
07Zapier, Make or n8n for Pingdom?
Pick on criteria, not on a ranking. On Zapier, Pingdom brings three polling triggers, one advanced action and no search, and works on the free plan. The deciding criterion is often speed: how fast must an alert reach your team, and which plan gives you that interval? The second is control: do you need more than relaying alerts, and can someone on the team write raw requests? Compare each tool on those two points.
Same platform

Other docs you might need on this stack.

Browse all integrations