Pendo Zapier integrationAutomate Pendo with Zapier.
The Pendo Zapier integration gives you 2 triggers, 0 actions and 0 searches. Both triggers watch a Pendo report and start a Zap when an account or a visitor matches its segment. Here is what they cost, how they fire and where they stop.
Verified Trustpilot reviews · AI, automation & growth agency
What the Pendo Zapier integration actually does
The Pendo Zapier integration links your Pendo analytics to the rest of your tools through Zapier. It works in one direction only: Pendo starts the automation, other apps do the work. A report in Pendo defines a segment, and Zapier picks up the accounts or visitors that land in it.
Three results you can build with it. A heads-up for the account team: Account in Report spots a customer account that matches the segment of a report, and the next step posts it where your account managers already read. A follow-up list of people: Visitor in Report brings each matching visitor into a Zap, so another app can add that person to a sheet, a CRM or an email sequence. A shared record of who matched: either trigger can feed a spreadsheet row per account or visitor, which gives product and sales the same list without anyone exporting it.
Now the part the app page skips. Zapier offers no action on Pendo here: a Zap cannot write anything back into Pendo, update an account or send a guide. There is no search step either, so a Zap cannot look up a Pendo record halfway through. And neither trigger is instant, so nothing reaches Zapier the second it happens in Pendo. If your plan depends on any of those, check the Zapier alternatives before you build.
The Zapier words, in plain English
Seven terms come back on this page. Each one is explained once, here.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. On this page, the triggers are Pendo report matches.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you. Pendo has none, so actions come from other apps.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those, nothing else.
- Polling vs instant
- Polling: Zapier checks the app on a timer and keeps only what is new. Instant: the app tells Zapier itself. Both Pendo triggers are polling.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set. Otherwise the run stops there.
- 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 Pendo Zap costs you
Pendo is not a premium app on Zapier, so it works on the free plan. The bill depends on the steps that come after the trigger, not on Pendo.
- Free plan100 tasks a month, unlimited Zaps
- Zap size on freeOne trigger and one action
- Pendo premium?No, available on the free plan
- Trigger checksFree, never billed
The trigger never costs a task, and the checks Zapier runs on your Pendo report cost nothing either, however often they happen. Each action that completes is one task; one that fails is not counted. The free plan stops at two steps, so adding a filter or a second action makes the Zap multi-step and moves you to a paid plan.
On the free plan Zapier checks your report every 15 minutes; Professional brings that to 2 minutes, Team and Enterprise to 1. A matching account that sits in a big segment can therefore start many runs, and each run pays for its own actions.
Connect your Pendo account in 3 steps
- 01
Open the connections page
In your Zapier account, go to Apps and click + Add connection. You need a Pendo account first, plus access to the reports you want the Zap to read if someone else owns them.
- 02
Pick Pendo in the list
Type Pendo in the search box of the dialog, select it, then click Add connection. A new tab opens on the Pendo side for the sign-in.
Keep that tab open until the sign-in is done.
- 03
Sign in and grant access
Log in to Pendo in that tab and give Zapier access to the account. The connection is then saved once and reused by every step that touches Pendo.
You will not repeat this per Zap.
Your first Zap: matching accounts to the team channel
GoalEach account that matches a Pendo report segment posts a message for the account team.
- 01
Build: pick the trigger
Create a Zap, choose Pendo as the app and Account in Report as the event, then select your Pendo connection. Pick the report whose segment defines the accounts you care about.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real account rather than a guess.
- 03
Add a filter if you need one
A filter is set in three boxes: the field to look at, the rule and the value. It keeps only the accounts you want, but it makes the Zap multi-step, so a paid plan is required.
- 04
Add the action and map it
Add the step in your messaging app and map the Pendo values from the trigger into the message. Test this step on its own and read what came back.
- 05
Publish
Publish the Zap to switch it on. From then on, Zapier checks your Pendo report on your plan's interval and runs the action for each new match.
Pendo triggers on Zapier
2 events start a Zap when something happens in Pendo. Zapier checks for them at the interval your plan allows.
Account in Report
Polling triggerIn Zapier“Triggers when an account matches a segment specified in a report.”
This one starts your Zap each time a customer account matches the segment set in a Pendo report. You point it at the report, and every account that newly fits comes through with its data for the next steps.
Visitor in Report
Polling triggerIn Zapier“Triggers when a visitor matches a segment specified in a report.”
Here the unit is a person, not a company. The Zap runs for each visitor who matches the segment of the Pendo report you chose, which lets you act on individual users instead of whole accounts.
When a Pendo Zap breaks
Zapier attaches no help article to Pendo, and no app-specific limit is documented. What breaks is what breaks on any Zapier trigger.
Four cases are worth knowing before you publish. When something looks wrong, the Zapier troubleshooting page is the place to start.
Past matches are never sent
A Zap only reacts to what happens after you switch it on. Accounts or visitors already in the report segment before that are not picked up; moving them is a separate job.A loop that eats your tasks
If the action writes into the very place a trigger watches, the Zap sets itself off again and again. With Pendo as a read-only source this is rare, but check any chained Zaps.A sudden flood is held back
When a report suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the run back instead of firing for every item.The same match only counts once
Zapier remembers what it already saw on a polling trigger, so an account or visitor does not start the Zap twice. Expect no repeat runs for someone who stays in the segment.
Need help automating Pendo with Zapier?
A person reads every message.
