Resources · Zapier integration

Pelcro Zapier integrationAutomate Pelcro with Zapier.

The Pelcro Zapier integration has 5 triggers, 4 actions and 0 searches. Every trigger is instant, so a new reader account or a fresh subscription in Pelcro reaches your other tools right away, and the actions let those tools write customers and subscriptions back.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pelcro Zapier integration is good for

Pelcro manages subscriptions and memberships. Linking it to Zapier lets customer, subscription and newsletter events in Pelcro start work elsewhere, and lets other tools create customers, subscriptions and newsletter records in Pelcro without anyone retyping them.

Three results worth building. A subscriber feed: Subscription Created posts each new subscriber to a channel or a sheet, so the revenue team sees sales as they land. A clean customer base: Customer Created and Customer Updated keep your CRM or mailing tool aligned with the reader accounts Pelcro holds. An inbound pipe: Create Customer and Create Subscription turn a sale closed in another tool into a real Pelcro account and plan, with Create Newsletter covering the people who only want the newsletter.

What Zapier does not do here: there is no search, so a Zap cannot look up an existing Pelcro customer before acting. There is no trigger for a cancelled or renewed subscription either, and no action to update a customer or a subscription; only newsletters can be edited, with Update Newsletter. If your process depends on churn or renewals, Pelcro's own tools have to cover that part.

All five triggers are instant, which removes the usual worry about the free plan being slow. To get the basics of the editor before you start, the Zapier training walks through them.

Vocabulary

Zapier vocabulary for a first Pelcro Zap

The words the editor uses, explained once in plain terms.

Zap
Your automation on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts a Zap, such as a new Pelcro customer. Once the Zap is on, Zapier waits for it.
Action
The step that does the work after the trigger: it writes, sends or moves something, for example a customer created in Pelcro.
Task
The unit Zapier bills: one action completed successfully. Your plan's allowance counts those, nothing else.
Instant vs polling
Instant: the app tells Zapier the moment something happens. Polling: Zapier checks on a timer. All Pelcro triggers are instant.
Filter
A step that lets the Zap go on only if what arrived meets your condition, and stops it there otherwise.
Connection
Your Pelcro account linked to Zapier once, then reused by every step that talks to Pelcro.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter or a second action makes one, and it needs a paid plan.
Cost

What Pelcro Zaps cost in tasks

The Pelcro trigger is free. Every action that works is not.

  • Cost of a Pelcro trigger0 tasks
  • Cost per successful action1 task
  • Free plan100 tasks a month, unlimited Zaps
  • Steps per Zap on the free plan2
  • Paid plan required for PelcroNo

A trigger never uses a task; each successful action uses one, so a Zap that creates a customer and then a subscription in Pelcro costs two tasks per run. A failed action is not counted. The free plan covers 100 tasks a month and unlimited Zaps, limited to two steps each: one trigger, one action. That second Pelcro action, or a filter, needs a paid plan. Pelcro is not restricted to paid plans. The interval grid below only concerns polling triggers, so it does not slow any Pelcro trigger.

Connect

Connect Pelcro to Zapier in 3 steps

  1. 01

    Start from Apps

    Open the Apps page of your Zapier account and click + Add connection. You do this once; every Pelcro step in every Zap reuses the same connection afterwards.

  2. 02

    Find Pelcro

    Search for Pelcro in the dialog, pick it, then click Add connection. You need an existing Pelcro account, with access to the data the Zap will read or write.

  3. 03

    Sign in and grant access

    Log in to Pelcro in the tab that opens and allow Zapier to use the account. The connection then shows up in the list, ready for your first trigger or action.

First Zap

Your first Pelcro Zap

GoalAdd every new Pelcro customer to the Pelcro newsletter and tell the team on Slack.

  1. 01

    Set the trigger

    Create a Zap, pick Pelcro as the starting app and Customer Created as the event, then select your Pelcro connection. A connection is set up once and reused.

  2. 02

    Test it on a real customer

    Run the trigger test. Zapier brings back the three most recent customers of the account, so you build the rest on genuine data.

  3. 03

    Add Create Newsletter

    Add a Pelcro step with Create Newsletter and map the customer's email into the email box, which is the one mandatory field.

  4. 04

    Add the Slack message

    Add the Slack step and write the message with values from the trigger. Two actions make it a multi-step Zap, which needs a paid plan.

  5. 05

    Test, then publish

    Test each action and check the newsletter record in Pelcro and the message in Slack. Then click Publish to switch the Zap on.

Triggers

The 5 Pelcro triggers

5 events start a Zap when something happens in Pelcro, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Customer Created

Instant trigger

In Zapier“Triggers when a user registers via the Pelcro Platform. This means that a customer record exists in Pelcro and has a unique email address, password, and customer ID associated to it.”

Starts the Zap when someone registers on your Pelcro platform and a customer record now exists with its own email and ID. This is the moment a reader becomes a known account, before any payment.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
push each new account into your CRM or welcome sequence so marketing can talk to them while they are still curious.
Watch out
if the same Zap also runs Create Customer in Pelcro, every new customer creates another one and the Zap loops.
2

Customer Updated

Instant trigger

In Zapier“Triggers when a user is updated or edited via the Pelcro Platform.”

Fires whenever a customer record is updated or edited on the Pelcro platform. It keeps downstream tools honest about who the person is today.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
update the matching contact in your mailing tool so an address change does not leave a stale copy behind.
Watch out
every edit is a new run, so busy accounts can trigger it many times; each run with a successful action costs a task.
3

Newsletter Created

Instant trigger

In Zapier“Triggers when a newsletter is created on the Pelcro Platform.”

Runs when a newsletter record is created on Pelcro. It is a separate event from customers and subscriptions, so it deserves its own Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
add the signup to your email platform's nurture list, separate from paying subscribers.
Watch out
a Zap that uses Create Newsletter elsewhere will also start this trigger, so avoid chaining the two into a circle.
4

Newsletter Updated

Instant trigger

In Zapier“Triggers when a newsletter is updated on the Pelcro Platform.”

Reacts to a change on an existing newsletter record in Pelcro. Where the previous trigger catches the signup, this one catches what happens to it afterwards.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
mirror the change in your mailing tool so both systems agree on who receives what.
Watch out
never pair it with Update Newsletter on the same record in one Zap; each update would set off the next one.
5

Subscription Created

Instant trigger

In Zapier“Triggers when a new subscription occurs via the Pelcro Platform.”

Fires when a new subscription comes in through Pelcro. It is the closest thing to a sale notification the integration offers, and the one most teams switch on first.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
log the sale in your revenue sheet, or ping the sales channel so the team sees it.
Watch out
it only covers new subscriptions; renewals and cancellations have no trigger on Zapier.
Actions

The 4 Pelcro actions

Pelcro gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Customer

Action

In Zapier“The create_customer action is to create a customer on the Pelcro Platform.”

Opens a customer account in Pelcro from data that arrives in another tool, such as a lead form or a checkout outside Pelcro.

When to use it
give every buyer from an event or partner sale a Pelcro account without manual entry.
Watch out
email is the only mandatory field; marketing consent options are there too, so map them rather than leaving them blank.
2

Create Newsletter

Action

In Zapier“The create_newsletter action is to create a newsletter on the Pelcro Platform.”

Creates a newsletter record in Pelcro for an email address coming from elsewhere, a landing page form or an event list for example.

When to use it
keep Pelcro as the single list of newsletter readers even when signups happen outside it.
Watch out
only the email is required, which makes it easy to send a blank one by mistake; test on a real record.
3

Create Subscription

Action

In Zapier“The create_subscription action is to create a subscription on the Pelcro Platform”

Attaches a subscription to an existing Pelcro customer. This is the heaviest action of the set, with five mandatory fields: plan id, user id, quantity, source and trial period days.

When to use it
activate access in Pelcro after a deal is signed in your CRM.
Watch out
without a user id from a previous step the action fails, so create or receive the customer first in the same Zap.
4

Update Newsletter

Action

In Zapier“The update_newsletter action is to update a newsletter on the Pelcro Platform”

Changes an existing newsletter record in Pelcro, and email is its one mandatory field. It is the only update action the integration offers.

When to use it
reflect a preference change made in your email platform back into Pelcro.
Watch out
map the email from the step before rather than typing it by hand, or every run edits the same record.
When it breaks

When a Pelcro Zap breaks

Zapier ties no help article and no rate limit to Pelcro.

The failures you will meet are general Zapier limits, and with Pelcro two of them matter more than usual because the app can both trigger and write. The Zapier troubleshooting page covers the generic fixes.

  • A Zap that writes where it listens

    Customer Created plus Create Customer, or Newsletter Updated plus Update Newsletter, in one Zap: each run sets off the next and the task count drains fast.

  • Existing customers are not picked up

    A Zap only reacts to events after it is published. Customers and subscriptions already in Pelcro stay out; moving them is a separate job.

  • A subscription with no customer

    Create Subscription needs a user id and a plan id. If no earlier step provides them, or the plan does not exist yet, the action fails.

  • Bulk imports can be held back

    Importing a large batch of customers into Pelcro can make a trigger send a huge burst; Zapier's flood protection may then hold those runs.
Need help

Need help automating Pelcro with Zapier?

A person reads every message.

FAQ

Pelcro Zapier integration: frequent questions

01Is the Pelcro Zapier integration free?
Yes. Zapier does not reserve Pelcro for paid plans, so it works on the free plan, which includes 100 tasks a month and unlimited Zaps. The limit is the size of each Zap: one trigger and one action. Sending a new customer to your CRM fits. Creating a customer and then a subscription in Pelcro from the same event takes two actions, so that Zap needs a paid plan. Each successful action in that Zap then counts as one task.
02How many tasks does a Pelcro Zap use?
Only actions count. The Pelcro trigger is free, and each action that completes successfully uses one task. A Zap that creates a customer and then a subscription uses two tasks per run, and a failed action is not counted. Customer Updated is the trigger to watch: every edit on a customer record is a run, so on an active base it can use more tasks than you expect. Watch the count on your plan page during the first weeks to see where the usage really comes from.
03Are Pelcro triggers real time?
Yes. All five Pelcro triggers are instant: Pelcro tells Zapier the moment a customer, newsletter or subscription event happens, and the Zap starts right away. The interval grid that delays polling triggers, 15 minutes on the free plan, does not apply. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is a quick way to check. No setting in the editor can change this: a trigger is instant or it is not, and the app decides.
04What does connecting Pelcro to Zapier require?
A Pelcro account, plus access to whatever data the Zap will read or write. In Zapier, open Apps, click + Add connection, search for Pelcro, sign in to Pelcro in the new tab and allow access. If you plan to use Create Subscription, also make sure the subscription plan already exists in Pelcro, because the action needs its plan id along with the customer's user id. The same connection then serves every Pelcro trigger and action in every Zap you build afterwards.
05Why does Create Subscription fail in a Pelcro Zap?
Usually because one of its five mandatory fields is empty: plan id, user id, quantity, source or trial period days. The user id is the classic gap, since it has to come from a customer that already exists or from a Create Customer step placed earlier. A plan id that points to no existing plan fails the same way. Test the action on a real customer before publishing. Map user id and plan id from earlier steps rather than typing them, so each run gets its own values.
06What if the Pelcro operation you need is missing?
Then the integration does not cover it today. Pelcro on Zapier offers 5 triggers and 4 actions: no search, no trigger for renewals or cancellations, and no action to edit a customer or a subscription. Any of these has to be handled in Pelcro itself. The practical workaround is to start the Zap from the events that do exist and let other apps do the rest of the work. Before building a workaround, check whether a trigger or action listed on this page already covers the need.
07Zapier, Make or n8n for Pelcro?
Judge on criteria, not on brand names. On Zapier, Pelcro gives you 5 instant triggers and 4 actions, works on the free plan as long as each Zap stays at two steps, and connects by signing in to your Pelcro account. If your flows are about new customers, new subscriptions and newsletters, that covers them. If you need renewals, cancellations or lookups, check what each platform offers for Pelcro first. Also weigh the task count: every successful Pelcro action costs one task on Zapier.
Same platform

Other docs you might need on this stack.

Browse all integrations