- Home
- Resources
- Integrations
- Plezi (Plus & Star)
Plezi (Plus & Star) Zapier integrationAutomate Plezi (Plus & Star) with Zapier.
The Plezi (Plus & Star) Zapier integration gives you 4 triggers, 2 actions and no search. Every trigger is checked on a timer, both actions work on contacts, and the app runs on the free plan. Here is what it does, what it costs and where it trips.
Verified Trustpilot reviews · AI, automation & growth agency
What the Plezi (Plus & Star) Zapier integration does
It links your Plezi (Plus & Star) marketing account to the other tools your team uses, through Zapier. Zapier can watch four kinds of contact moments in Plezi (a content request, a new contact, a changed contact, a contact turning MQL) and Zapier can write back two things: a scoring event, or a contact it creates or updates.
Three outcomes cover most of what people build with it. A warmer score: a request for a key piece of content runs Create Contact Event, which adds the points you choose to that contact's score. A handoff to sales: MQL Contacts starts a Zap once a contact crosses Plezi's threshold, so the lead lands in the tool your sales team actually opens. One contact base, not two: sign-ups from a webinar tool or a form go through Create or Update Contact, which updates the person if the email exists and creates them otherwise.
Now what Zapier does not do here. There is no search step, so a Zap cannot look up a Plezi contact to reuse its details further down. There is no delete action and nothing on content, campaigns or forms themselves. And no trigger is instant: all four are polled, so on the free plan a content request can wait up to 15 minutes before the Zap moves.
If those gaps matter, the Make vs Zapier and n8n vs Zapier pages are worth a read before you commit, and our Zapier review gives the wider picture.
Zapier vocabulary, in plain words
Eight words carry the rest of this page. Each one is used exactly as below from here on.
- Zap
- The automation you build on 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 switched on, Zapier waits for that event and nothing else.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling trigger
- A trigger Zapier checks on a timer. It asks the app for new items at a fixed interval and keeps only the ones it has not seen.
- Instant trigger
- A trigger the app reports itself, the moment the event happens. Plezi (Plus & Star) has none of these today.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set, and stops it quietly otherwise.
- Multi-step Zap
- Any Zap beyond one trigger plus one action. A second action or a filter makes it one, and then it needs a paid plan.
What a Plezi (Plus & Star) Zap really costs
Plezi (Plus & Star) is not a premium app, so the free plan can use it. The bill comes from actions, never from the checking.
- Free plan100 tasks a month, unlimited Zaps
- Zap length on freeOne trigger and one action
- Premium appNo, available from the free plan
- Trigger costZero tasks, on every check
Each time Zapier looks at Plezi for new contacts, it costs nothing, however often it looks. A task is counted only when an action goes through: a scoring event logged, a contact created or updated. An action that fails is not counted. A Zap that runs two actions on the same contact spends two tasks. The free plan stops at two steps, so adding a filter in front of Create Contact Event already means a paid plan.
Connect your Plezi (Plus & Star) account
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Plezi account linked once, then reused by every step that touches Plezi.
- 02
Pick Plezi (Plus & Star)
Type the app's name in the dialog, select Plezi (Plus & Star) in the results, then click Add connection. Check you picked this exact entry, with Plus & Star in the name.
- 03
Sign in and grant access
Sign in to Plezi in the tab that opens, then allow Zapier into the account. You need a Plezi account, plus write access to any contacts you do not own and want the Zap to change.
Your first Zap: score content requests and tell sales
GoalEach time a contact asks for a chosen content, add points to their Plezi score and send the rep an email.
- 01
Build: set the trigger
Create a Zap, pick Plezi (Plus & Star) and the event Contacts That Asked for Content. In the Content box, choose the asset that signals buying intent, such as a pricing guide.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent content requests from your account, so you can map the next steps on a real contact instead of a blank.
- 03
Add the scoring action
Add Create Contact Event. Map the contact's email into Contact email, write a short Description your marketers will recognise, and set the Points to add.
- 04
Add the email to sales
Add a Gmail step that writes to the account owner. This third card makes the Zap multi-step, so it needs a paid plan. On free, keep only the scoring action.
- 05
Test, then publish
Test each step and read what came back, then click Publish. From then on, only new requests are picked up: older ones stay where they are.
The 4 Plezi (Plus & Star) triggers
4 events start a Zap when something happens in Plezi (Plus & Star). Zapier checks for them at the interval your plan allows.
Contacts That Asked for Content
Polling triggerIn Zapier“Triggers when a contact fills a form to ask for some content”
Starts the Zap when a contact fills a Plezi form to get one of your contents, like a white paper or a checklist. You pick which content to watch, so one Zap follows one asset.
Contacts Created
Polling triggerIn Zapier“Triggers when a contact is created.”
Fires for every new contact Plezi records, whatever brought them in. It is the broadest entry point of the app: no setting narrows it down at the trigger itself.
Contacts Recently Changed
Polling triggerIn Zapier“Triggers when a contact is updated.”
Picks up contacts whose record was edited in Plezi, so other tools stay in line with what marketing knows about a person. Each update after the Zap goes live counts.
MQL Contacts
Polling triggerIn Zapier“Triggers when a contact become a MQL so has the score defined by MQL threshold.”
Fires when a contact reaches the score set by your MQL threshold in Plezi, the point where marketing considers the lead qualified. It is the cleanest handoff signal the app offers.
The 2 Plezi (Plus & Star) actions
Plezi (Plus & Star) gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Contact Event
ActionIn Zapier“Creates a contact event with a custom description and a number of points to add to the contact score”
Logs an event on a contact with your own description and adds a number of points to their score. It is how actions outside Plezi count toward lead scoring.
Create or Update Contact
ActionIn Zapier“Updates a contact. If the email address is not found, the contact will be created”
Sends a person into Plezi: if the email address already exists, the contact is updated, otherwise a new one is created. No duplicate to clean up afterwards.
When a Plezi (Plus & Star) Zap breaks
Zapier attaches no help article to Plezi (Plus & Star), so the known failures are the general ones. On this app, they hit in specific places.
Most trouble comes from the timer and from writing back into Plezi. If a run looks wrong, the Zapier troubleshooting page is the next stop.
Old contacts never come through
A Zap only reacts to what happens after it is published. Contacts and requests already in Plezi stay put; moving that backlog is a separate job.A Zap that restarts itself
Contacts Recently Changed followed by Create or Update Contact on the same account writes into what the trigger watches. It loops and eats tasks.A big import stalls the Zap
A bulk import of contacts makes a trigger return a huge batch at once. Zapier's flood protection can hold that batch back instead of running it.No duplicate runs, by design
Zapier remembers which contacts a polling trigger already saw, so the same item does not start the Zap twice, even if it shows up in two checks.
Need help automating Plezi (Plus & Star) with Zapier?
A person reads every message.



