Connect Zapier

The Pingstack Zapier integration connects your account to thousands of other apps. Use it for destinations Pingstack doesn’t deliver to directly, and to let other apps act on your monitoring. It is available on every plan.

Connect your account

You start the connection in Zapier, not in Pingstack.

1. In Zapier, create a Zap and choose Pingstack as the trigger or action app.
2. Choose Sign in. Zapier opens Pingstack’s Connect Zapier to Pingstack? page. Sign in to Pingstack if asked.
3. Choose the account. Only accounts where you are an Owner or Admin are listed, and each connection is limited to one account.
4. Review the permissions and choose Allow access. To use Send Ping, also tick Retrieve heartbeat ping URLs; it is unticked by default because ping URLs are credentials.
5. Back in Zapier, the connection is named after the Pingstack account.

The Channels page also has a Zapier card in Supported integrations. It shows whether the account is connected, and Owners and Admins can open Zapier from its Connect Zapier button.

The connection acts as the person who approved it. Every request also checks that person’s current role: if they lose access to the account, so does the connection. Post Incident Status Update posts as that person.

Manage or disconnect Zapier

Open Settings → Developer → Connected apps. Zapier is listed under Active connections with who approved it, when it was last used and how many event subscriptions it has. Choose Disconnect to end the connection immediately; its triggers stop and its event subscriptions are deleted.

A Zapier connection stays active while it’s in use. It expires after 90 days with no API use, no delivered events and no active trigger subscriptions.

Triggers

Triggers fire within seconds of the event. Each one has an optional Check field; leave it empty to trigger for every check in the account.

Trigger	Fires when
Check Is Down	A check goes down
Check Is Degraded	A check becomes degraded
Check Recovered	A down or degraded check is back up
New Incident	An incident opens
Incident Updated	An open incident changes severity, or someone posts a status update to it
Incident Resolved	An incident resolves because its check recovered

A check moving between degraded and down fires both the check trigger and Incident Updated. A new check reporting for the first time fires nothing.

Each event includes:

Field	Meaning
Alert Text	Human-readable summary, for messages
Check ID, Check Name, Check Kind	The check
Check Target	Hostname, host and port, or website URL without credentials or query string; empty for heartbeat checks
Check Status, Previous Check Status	Status after and before the change
Check URL	Link to the check in Pingstack
Incident ID, Incident Cause, Incident Started At, Incident Resolved At	The incident, when there is one
Update Text, Update Author, Update Posted At	Incident Updated only, when it was triggered by a posted update

Incident causes and update text are included. Choose destinations for these Zaps accordingly.

When you test a trigger, Zapier loads up to three recent matching incidents from your account. If there are none yet, it shows an example event.

Actions

Action	What it does	Permission needed
Send Ping	Records a heartbeat for a heartbeat check, optionally at a named location and with a number for value thresholds	Retrieve heartbeat ping URLs
Create Check	Creates a website check (URL, interval, expected status code) or heartbeat check (expected interval, grace period)	Create checks
Pause Check	Pauses a check so it stops running and alerting	Update checks
Resume Check	Resumes a paused check; it starts again from pending	Update checks
Post Incident Status Update	Adds an update to an open incident	Post incident updates

Actions also need the approving person’s role to allow them. Editors and Admins can create, pause and resume checks and post incident updates. Create Check counts toward your plan’s check limit.

Searches

Search	Returns
Find Check	Checks whose name matches, exact matches first. Find or Create Check creates the check if none matches.
Find Open Incident	The selected check’s open incident

Use Find Open Incident before Post Incident Status Update when the Zap starts from something other than a Pingstack trigger.

For example Zaps, see Zapier recipes. To build your own integration on the same events, see event subscriptions.