- Home
- Resources
- Integrations
- Pingback
Pingback Zapier integrationAutomate Pingback with Zapier.
The Pingback Zapier integration gives you 8 triggers, 0 actions and 0 searches. All 8 triggers are instant: new contacts, list moves, form conversions and email activity reach Zapier without waiting for a scheduled check, even on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What Pingback can start in Zapier, and what it cannot
Pingback on Zapier works in one direction. When a contact appears, changes, joins or leaves a segmented list, converts on a form, or receives, opens or clicks an email, Zapier hears about it and runs the steps you chose in your other tools. It listens to Pingback. It never writes back into it.
Three results people build with it. A hot-lead alert: Email Clicked watches one link in one email, and each click becomes a message for your sales team. A mirrored segment: Added to Segmented List and Remove From Segmented List keep a spreadsheet or another tool in step with a Pingback segment, entries and exits included. A form handoff: Conversion Created passes every new form conversion to the next tool in your sales process.
Now the limits. Zapier offers no action and no search for Pingback. A Zap cannot create a contact in Pingback, edit one, put it in a list or look it up. Pingback is always the first card of the Zap, and everything after it happens somewhere else. If your plan depends on writing into Pingback, this integration will not carry it (check the Make vs Zapier page before you commit to a tool).
The good news sits on the other side: every trigger is instant, so the free plan loses nothing on speed here.
Zapier words, in plain English
Eight terms come back on this page. Here is what each one means for a Pingback user.
- 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. With this integration it is always something in Pingback, such as a contact created or an email opened.
- Action
- What the Zap does once started: the step that writes, sends or moves something. Pingback offers none, so it lives in another app.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts nothing else.
- Instant vs polling
- An instant trigger is reported by the app itself. A polling trigger is checked by Zapier on a timer. All 8 Pingback triggers are instant.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it right there otherwise.
- Connection
- Your Pingback account linked to Zapier once, then reused by every step of every Zap that touches Pingback.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter turns it into one, and it then needs a paid plan.
What a Pingback Zap costs you in tasks
A Pingback trigger never costs a task. Zapier only bills actions that went through.
- Trigger cost0 tasks
- Free plan100 tasks a month
- Steps per Zap on Free2: one trigger, one action
- Premium appNo, it works on Free
One email opened, one Slack message sent: one task. Add a second action and each success counts on its own, while an action that fails is not billed at all. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, so adding a filter pushes you onto a paid plan. The polling grid below does not apply to this app: Pingback reports each of its events to Zapier itself, whatever your plan.
Connect Pingback to Zapier in three steps
- 01
Find Pingback 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 Pingback and pick it in the results.
- 02
Sign in to your Pingback account
Click Add connection, then sign in to Pingback in the tab that opens. Use the account that holds the contacts, lists and emails your Zaps will watch, or one with read access to them.
- 03
Grant access and reuse it
Approve the access Zapier asks for on that account. From there, every Zap and every step that uses Pingback picks this same connection, so the sign-in happens once, not once per Zap.
Your first Pingback Zap: a sales alert on new list members
GoalEach contact added to a chosen Pingback segment that passes your rule becomes a Slack message for the sales team.
- 01
Pick the app and the event
Start building: choose Pingback as the app that starts the Zap, then Added to Segmented List as the event, and select your Pingback connection.
- 02
Choose the segment
Pick the segmented list in the trigger settings. It is required, so the segment has to exist in Pingback before this step. The editor shows a lightning bolt: this trigger is instant.
- 03
Test on real contacts
Run the test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real contact instead of a made-up one.
- 04
Add the filter
Click the plus icon, choose Filter, then fill the three boxes: the field to look at, the rule, the value. Pick a text rule for text, a number rule for numbers. This step makes the Zap multi-step.
- 05
Add the Slack action and publish
Add the action in the other app, map the contact details you saw in the test, run the step once and read what came back. Then click Publish to switch the Zap on.
The 8 Pingback triggers
8 events start a Zap when something happens in Pingback, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.
Added to Segmented List
Instant triggerIn Zapier“Triggers when a contact is added to a segmented list.”
Starts a Zap each time Pingback puts a contact into the segmented list you picked. Your other tools learn who just entered that segment, and nobody has to export a file or copy names across.
Contact Created
Instant triggerIn Zapier“Triggers when a new contact is created.”
Fires on every brand-new contact in Pingback, wherever it came from. It is the widest net of the eight, which makes it the natural start for copying your audience into a CRM or a sheet.
Contact Updated
Instant triggerIn Zapier“Triggers when a new contact is updated.”
Runs your Zap whenever an existing Pingback contact gets updated. Pair it with Contact Created when another tool must hold the latest version of each person, not only the first one.
Conversion Created
Instant triggerIn Zapier“Triggers when you have a new conversion from a Form.”
Turns each new conversion from a Pingback form into the start of a Zap. Someone fills in the form, and the next tool in your process gets the hand-off straight away.
Email Clicked
Instant triggerIn Zapier“Triggers when a link is clicked inside the email.”
Reacts to a click on one link inside one Pingback email. Of the three email triggers, this one carries the clearest signal of intent, because the reader acted instead of just opening.
Email Delivered
Instant triggerIn Zapier“Triggers when the email is delivered.”
Fires when a chosen Pingback email reaches a contact's inbox. It confirms delivery, not reading, which makes it useful for records rather than for sales alerts.
Email Opened
Instant triggerIn Zapier“Triggers when the email is opened.”
Starts the Zap when a contact opens the Pingback email you selected. It sits between delivery and click: the message got attention, even if nobody acted on it yet.
Remove From Segmented List
Instant triggerIn Zapier“Triggers when a contact is removed from a segmented list.”
The mirror of Added to Segmented List: it fires when a contact leaves the segment you picked. Without it, a copy of your segment elsewhere only ever grows and slowly goes stale.
When a Pingback Zap breaks
Zapier ties no help article to Pingback and lists no limit of its own for it. What breaks is the general Zapier behaviour, and it bites harder on an app that only starts Zaps.
Four cases come back most often. If a Zap still misbehaves after these, the Zapier troubleshooting page is the next stop.
The old contacts never arrive
A Zap only reacts to what happens after you switch it on. Contacts, conversions and clicks from before stay in Pingback; moving that backlog is a separate job.A bulk import gets held back
Import a big batch of contacts and Contact Created suddenly reports a flood of events. 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 only works on text, a number rule only on numbers. Pick the wrong type 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 your Pingback trigger turns the Zap multi-step, which needs a paid plan.
Need help automating Pingback with Zapier?
A person reads every message.



