Pinghome Zapier integrationAutomate Pinghome with Zapier.
The Pinghome Zapier integration has 1 trigger, 0 actions and 0 searches. That trigger, State Change, fires when a monitored resource goes from up to down or back up, and it is instant: your Zap does not wait for a scheduled check, even on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What Pinghome can start in Zapier
Pinghome on Zapier does one thing, and it does it fast. When one of your monitored resources changes state, from up to down or from down to up, Pinghome tells Zapier, and the Zap carries that news to the tools where your team actually works. Zapier listens to Pinghome; it never changes anything inside it.
Three results come out of that single trigger. An incident ping: State Change posts the outage in the channel the on-call person watches, and posts again when the resource recovers. An incident log: each change becomes a row in a shared sheet, so the team can look back at what went down and when it came back. A ticket opener: a down event creates a ticket in your support tool, so nobody has to remember to file one in the middle of an outage.
The limits are just as short. There is no action and no search for Pinghome on Zapier: a Zap cannot pause a monitor, add a resource or look one up. Pinghome is always the first card, and everything after it happens in another app. And the trigger covers state changes only, so anything else Pinghome tracks stays out of reach here.
The upside is speed: the trigger is instant, so the free plan loses nothing on reaction time. To compare with other automation tools, see Make vs Zapier.
Zapier vocabulary for Pinghome users
Eight terms, one plain line each, as they apply to a Zap that starts with Pinghome.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event that starts a Zap. Here it is State Change, a Pinghome resource going down or coming back up.
- Action
- What the Zap does once started: the step that writes, sends or moves something. Pinghome offers none, so it lives in another app.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Each message sent about an outage is one task.
- Instant trigger
- A trigger the app reports itself, so nothing waits for the next check. State Change is one, and shows a lightning bolt in the editor.
- Polling trigger
- A trigger Zapier checks on a timer, at an interval set by your plan. Pinghome has none, which is good news for outages.
- Filter
- A step that lets the Zap carry 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 turns it into one, and it then needs a paid plan.
What a Pinghome Zap costs in tasks
The State Change trigger never costs a task. Zapier only bills the actions that follow, and only when they work.
- Trigger cost0 tasks
- Free plan100 tasks a month
- Steps per Zap on Free2: one trigger, one action
- Premium appNo, it works on Free
One outage, one chat message: one task. Then the recovery, one more. Each extra 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, with two steps per Zap: a filter, or a second action, puts you on a paid plan. The polling grid below does not apply here, because Pinghome reports each change to Zapier itself, whatever your plan.
Connect Pinghome to Zapier in three steps
- 01
Find Pinghome from the Apps page
In your Zapier account, open the Apps page and click + Add connection. A dialog lets you search apps by name: type Pinghome and pick it in the results.
- 02
Sign in to Pinghome
Click Add connection, then sign in to Pinghome in the tab that opens. Use the account of the team that owns the resources you want to watch, or one with read access to them.
- 03
Grant access
Approve the access Zapier asks for. Every Zap and every step that uses Pinghome then reuses this connection, so a second alert Zap for another team channel needs no new sign-in.
Your first Pinghome Zap: outages only, straight to chat
GoalEvery time a chosen Pinghome resource goes down, and only then, the incident channel gets a message.
- 01
Pick Pinghome and State Change
Start building with Pinghome as the app that starts the Zap and State Change as the event, then select your Pinghome connection.
- 02
Choose the resources
In the Resource List, pick the resources that matter, or all of your team's resources. The setting is required. The editor shows a lightning bolt: this trigger is instant.
- 03
Test on recent changes
Run the test. Zapier brings back the three most recent items of the connected account, so you build the rest of the Zap on a real state change, not a made-up one.
- 04
Keep only outages
Click the plus icon, choose Filter and fill the three boxes: the state field, a text rule, the value for down. The Zap becomes multi-step and needs a paid plan.
- 05
Add the chat action and publish
Add the message action in your chat app, map the resource details from the test, run the step once and read what came back. Then click Publish.
The Pinghome trigger
1 event starts a Zap when something happens in Pinghome, and one of them is instant: the app calls Zapier straight away, whatever your plan.
State Change
Instant triggerIn Zapier“Triggers when resource state either changed from up to down or from down to up.”
Starts a Zap whenever a Pinghome resource flips state, from up to down or from down to up. One trigger covers both the outage and the recovery, so the same Zap can open and close the loop for your team.
When a Pinghome Zap breaks
Zapier ties no help article to Pinghome and records no limit of its own for it. The breakdowns come from general Zapier rules, and on a monitoring tool they tend to show up on a bad day.
Four cases cover most problems. If yours is not here, go through Zapier troubleshooting.
Past outages never arrive
A Zap only reacts to what happens after you switch it on. State changes from before stay in Pinghome; collecting that history is a separate job.A big incident gets held back
When many resources flip at once, the trigger can report a huge batch in one go. Zapier's flood protection can hold that batch back instead of running it.The filter never lets anything through
Filter rules are typed: a text rule works on text, a number rule on numbers. Compare a state with a number rule and the condition never passes.The Zap will not publish on Free
The free plan builds two-step Zaps only. A filter or a second action after State Change makes the Zap multi-step, which needs a paid plan.
Need help automating Pinghome with Zapier?
A person reads every message.
