Resources · Zapier integration

Plerdy Zapier integrationAutomate Plerdy with Zapier.

The Plerdy Zapier integration gives you 1 trigger, 0 actions and 0 searches. Every email address your Plerdy pop-ups collect can start a Zap and land in your email platform, your CRM or a spreadsheet, without exporting lists by hand. It runs on the free plan.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Plerdy Zapier integration is for

Plerdy runs pop-ups on your website, with more than 25 display conditions, to collect emails and sign-ups from visitors. On Zapier it does one job: each new email it collects can start a Zap that carries the address to another tool. Nothing flows back into Plerdy.

Three outcomes built on the single Emails trigger. A newsletter list that grows on its own: the address goes straight to your email platform as a subscriber, instead of sitting in Plerdy until someone exports it. A lead log the sales team actually reads, instead of a list buried in a dashboard: the same trigger writes each address into a CRM or a shared spreadsheet. An alert for hot campaigns: a message in your team chat each time a launch pop-up collects someone.

What Zapier does not do for Plerdy. There is no action, so a Zap cannot create a pop-up, change a condition or add a contact inside Plerdy. There is no search step either. The only trigger works by polling, so addresses reach the next tool on Zapier's schedule, not the second a visitor submits. And the trigger covers collected emails only: no other Plerdy event is available on Zapier.

Still choosing a platform? See Zapier alternatives.

Vocabulary

Zapier words, in plain English

Eight words cover everything below.

Zap
The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap. For Plerdy, it is a new email collected by one of your pop-ups.
Action
What the Zap does once started: the step that writes, sends or moves something for you, here in another app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully; your plan counts those.
Polling trigger
A trigger Zapier checks on a timer: it asks Plerdy for new emails at a fixed interval and keeps only unseen ones.
Instant trigger
A trigger the app reports itself, the moment the event happens. The Plerdy trigger is not one of these.
Filter
A step that lets the Zap go on only when the incoming item meets your condition, and stops it otherwise.
Connection
Your Plerdy account linked to Zapier once, then reused by every Zap that starts from Plerdy.
Cost

What it really costs

Plerdy is not a premium app, so it works on the free plan. The Emails trigger never costs a task, and Zapier checking Plerdy for new addresses is free as well, however often it looks.

  • Free plan100 tasks a month, unlimited Zaps
  • Zap size on free2 steps: one trigger, one action
  • Trigger cost0 tasks
  • Premium appNo

You pay one task per action that succeeds in the other tool. One address added to your newsletter costs one task; add a chat alert in the same Zap and that address costs two. A failed action is not counted. Your task count therefore follows the number of emails your pop-ups collect. On the free plan a Zap stops at two steps, one trigger and one action. A filter or a second action makes it multi-step, which needs a paid plan.

Connect

Connect your Plerdy account

  1. 01

    Add the connection

    In Zapier, open the Apps page of your account and click + Add connection. In the dialog that appears, type Plerdy in the search box and pick it from the list.

  2. 02

    Sign in to Plerdy

    Click Add connection. A new tab opens on Plerdy. Sign in with the account that owns the website and the pop-ups whose emails you want to send on to other tools.

  3. 03

    Grant access

    Allow Zapier to reach the Plerdy account. The connection is then reused by every Zap that starts from Plerdy, so you set it up once and pick it from a list afterwards.

First Zap

Your first Zap: pop-up emails to your newsletter

GoalEach address collected by a Plerdy pop-up is added as a subscriber in your email platform.

  1. 01

    Pick the trigger

    Create a Zap, choose Plerdy as the app and Emails as the event, then select your Plerdy connection. It is the only event on offer.

  2. 02

    Test with a real address

    Run the test. Zapier brings back the three most recent emails collected, so the mapping in the next steps uses a real submission.

  3. 03

    Add a filter (paid plans)

    To keep colleagues' test sign-ups out, add a filter: the field, the rule, the value. A filter makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the subscriber step

    Add your email platform, choose the list, and map the address from the trigger. On the free plan, skip the filter and keep these two steps only.

  5. 05

    Test, then publish

    Test the action and check the new subscriber. Click Publish to switch the Zap on. Emails collected before that moment will not be sent across.

Triggers

The Plerdy trigger

1 event starts a Zap when something happens in Plerdy. Zapier checks for them at the interval your plan allows.

1

Emails

Polling trigger

In Zapier“Triggers when a new Emails to Plerdy.”

Starts a Zap when a new email reaches Plerdy through one of your pop-ups. The address is handed to the next step, so it can go wherever your follow-up actually happens.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
an online shop runs a discount pop-up and wants each address in its email tool before the welcome sequence goes out.
Watch out
it is the only Plerdy trigger, so every Zap starts here, and on the free plan a new address can wait up to one interval before it moves.
When it breaks

When it breaks

Zapier links no help article to Plerdy, and no app-specific limit is documented. The cases below are general Zapier limits as they apply to this one trigger.

With a single trigger, trouble rarely comes from errors. It comes from history, volume and timing. Run through these four cases, then the Zapier troubleshooting page.

  • Older emails never arrive

    A Zap only reacts to what happens after you switch it on. Addresses Plerdy collected earlier are not picked up; moving that list is a separate job.

  • A campaign spike gets held back

    When the trigger suddenly returns a huge batch, after a viral pop-up or a list import, Zapier's flood protection can hold those emails back instead of running them all.

  • The same address is not sent twice

    Zapier remembers what it has already seen on a polling trigger, so one submission does not start the Zap twice, even when the trigger is checked again.

  • The filter step asks for an upgrade

    On the free plan a Zap holds two steps only. A filter or a second action turns it into a multi-step Zap, and Zapier then asks for a paid plan.
Need help

Need help automating Plerdy with Zapier?

A person reads every message.

FAQ

Plerdy Zapier integration: FAQ

01Is the Plerdy Zapier integration free?
Yes. Plerdy is not a premium app on Zapier, so its Emails trigger works on the free plan. That plan gives 100 tasks a month and unlimited Zaps, with one limit that surprises people: each Zap holds two steps, one trigger and one action. A filter, a search or a second action makes the Zap multi-step, and that needs a paid plan. No price is quoted here, because plan grids change often; check them on Zapier before you upgrade.
02How many tasks does a Plerdy Zap use?
The trigger itself costs nothing, and neither do Zapier's checks for new emails, however frequent. You pay one task per action that succeeds. A Zap that adds each collected address to your newsletter uses one task per address; add a chat alert and it uses two. A failed action is not counted. In practice, your monthly task count follows the number of emails your pop-ups collect, multiplied by the actions in the Zap.
03Does the Plerdy trigger work in real time?
No. Emails is a polling trigger: Zapier asks Plerdy for new addresses at a fixed interval and keeps only the ones it has not seen. The interval depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. The type is set by the app and cannot be changed from the editor. On paid plans you can also run a check by hand from the editor when a result is needed right away.
04What does it take to connect a Plerdy account?
A Plerdy account, plus access to the site and pop-ups you want the Zap to read if you do not own them yourself. The connection takes three moves: + Add connection on the Apps page, sign in to Plerdy in the tab that opens, then grant Zapier access. Before testing, make sure at least one email has been collected, since the test brings back the three most recent ones. Without that, there is nothing to map yet.
05Why does the Plerdy trigger test come back empty?
Because the test can only bring back emails that already exist. Zapier pulls the three most recent addresses collected on the connected account; on a new pop-up or a quiet site there may be none. Submit a test address through the pop-up on your own site, then run the test again. You will then map fields on a real submission, which is safer than guessing what the trigger returns. Delete the test entry afterwards in the destination tool if it should not stay.
06What if the Plerdy operation you need is missing?
Then Zapier does not offer it for Plerdy today. The editor lists a single trigger, Emails, and nothing else: no action, no search, no trigger for other Plerdy data. A Zap can carry collected addresses to other tools, but it cannot create or change anything inside Plerdy. If your workflow needs more, plan that part outside Zapier or keep it as a manual step in Plerdy. Knowing that up front saves a long search through the editor menus.
07Zapier, Make or n8n for Plerdy?
Decide by criteria rather than by brand. On Zapier, Plerdy exposes one polling trigger for collected emails, with no action and no search, and it runs on the free plan while each Zap stays at two steps. So the questions are: is a new email the only event you need, can you live with your plan's polling interval, and how many steps will your Zap need? Then check whether the other platform's Plerdy connector covers those exact points.
Same platform

Other docs you might need on this stack.

Browse all integrations