Resources · Zapier integration

Peggy Pay Zapier integrationAutomate Peggy Pay with Zapier.

The Peggy Pay Zapier integration gives you 12 triggers, 0 actions and 0 searches. All of them are instant: a paid order, a failed installment or a cancelled subscription on one of your payment pages starts the automation right away, free plan included.

See the 12 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Peggy Pay Zapier integration actually does

Peggy Pay builds payment pages, surveys and web forms. Hooking it to Zapier means each thing that happens on those pages (a new payment, an installment that fails, a subscription that ends) can kick off work in your other tools. Peggy Pay only talks; the other apps do the writing.

Three results people usually build. A payment log: 1. New Payment or Submission drops every paid order or form entry into a spreadsheet, so finance stops copying rows by hand. A dunning alert: Subscription Payment Failed and Installment Payment Failed warn whoever chases unpaid invoices, before the customer forgets about it. A churn feed: Subscription Cancelled by Customer tells your sales or support team who just left, while Subscription Reactivated by You closes the loop when someone comes back.

Now the part the app page does not spell out. Zapier offers no action and no search for Peggy Pay. A Zap can listen to your payment pages, but it cannot create an order, edit a subscription, refund anyone or look up a past payment there. Anything that has to change inside Peggy Pay stays a manual job. And because there is no Peggy Pay action, every Zap you build here ends in a different app.

Good news on speed, though: every one of the 12 triggers is instant, so the plan you are on never slows them down. If you are still weighing tools, the Make vs Zapier and n8n vs Zapier pages sit next to this one.

Vocabulary

Zapier words, in plain English

Seven words you will meet in the editor, each explained once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event that starts the Zap. Here it is always something on a Peggy Pay page; once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something. With Peggy Pay, actions live in your other apps.
Task
What Zapier bills you for: one action that completes successfully. The number on your plan is a count of those.
Instant vs polling trigger
An instant trigger is reported by the app the moment the event happens. A polling one is checked by Zapier on a timer. Peggy Pay only has instant ones.
Filter
A step that lets the Zap continue only when what arrived matches the condition you set, and stops it otherwise.
Multi-step Zap
Anything beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
Cost

What a Peggy Pay Zap really costs

Listening to Peggy Pay is free. You pay for what happens next.

  • Cost of a Peggy Pay trigger0 tasks
  • Free plan100 tasks a month, unlimited Zaps
  • Steps per Zap on the free plan2 (one trigger, one action)
  • Paid plan required for Peggy PayNo
  • Instant triggers12 of 12

A Peggy Pay trigger never uses a task. Only the actions after it do, and only when they succeed: a Zap with three actions eats three times what a one-action Zap eats, and an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, one trigger and one action. Add a filter or a second action and you need a paid plan. Peggy Pay itself is not reserved for paid plans. The interval grid below only matters for polling triggers, so none of it applies to this app.

Connect

Connect Peggy Pay to Zapier in 3 steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Peggy Pay account linked once, then reused by every step that needs it.

  2. 02

    Pick Peggy Pay

    Type Peggy Pay in the search box of the dialog, select it, then click Add connection. You need an existing Peggy Pay account; Zapier does not create one for you.

  3. 03

    Sign in and allow access

    Log in to Peggy Pay in the tab that opens and grant Zapier access to the account. If the pages you want to watch belong to someone else, make sure you have access to them first.

First Zap

Your first Peggy Pay Zap

GoalLog each failed subscription charge in a sheet and email the person who handles collections.

  1. 01

    Pick the trigger

    Create a Zap, choose Peggy Pay as the app that starts it and Subscription Payment Failed as the event. Select your Peggy Pay connection.

  2. 02

    Choose the form

    Set the Form box to the subscription page you want to watch. That field is mandatory, and only the page you pick feeds this Zap.

  3. 03

    Test the trigger

    Run the test. Zapier pulls back the three most recent items from the account so you map the next steps on a real failed charge, not on placeholders.

  4. 04

    Add the two actions

    Add the sheet step, then the email step, and map the Peggy Pay values into each box. Two actions make this a multi-step Zap, so it needs a paid plan.

  5. 05

    Test each step

    Run every action once and read what came back: a new row in the sheet, an email in the right inbox. Fix the mapping now rather than after a real customer fails a charge.

  6. 06

    Publish

    Click Publish to switch the Zap on. From then on each failed subscription charge on that page lands in the sheet and in the inbox.

Triggers

The 12 Peggy Pay triggers

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

1

New Installment

Instant trigger

In Zapier“Triggers when a new installment is created.”

Starts the Zap when a customer opts for paying in several parts and Peggy Pay creates the installment plan. Useful for anyone who needs to know a split payment is now running, before the first part is even collected.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
open a follow-up card in your project tool each time a client commits to a payment schedule.
Watch out
the trigger asks for a Form, so one Zap covers one page; a second page needs its own Zap.
2

Installment Payment

Instant trigger

In Zapier“Triggers when a installment payment has succeeded.”

Fires each time one part of an installment plan goes through. You get one run per successful part, not one per plan, which makes it the right event to track money actually received.

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 a line to your bookkeeping sheet for every part paid, so the balance of each plan stays visible.
Watch out
each run that leads to a successful action costs a task, so long schedules add up on a busy page.
3

Installment Payment Failed

Instant trigger

In Zapier“Triggers when a installment payment has failed.”

Reacts when a scheduled part of an installment plan does not go through. This is the early warning: the customer is still on the plan, but one charge has bounced and someone should look at it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
send a polite reminder email, or ping the person in charge of collections, while the failure is still fresh.
Watch out
pick the same Form as your success Zap, otherwise one page gets alerts and the other does not.
4

Order Status Changed

Instant trigger

In Zapier“Triggers when a order status has been changed.”

Runs whenever the status of an order moves in Peggy Pay. Instead of watching only for new orders, you follow what happens to them afterwards, which suits teams that ship or deliver after 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
update the matching row in your fulfilment sheet each time an order changes stage.
Watch out
every status change is a new run; add a filter (paid plan) if only one status matters to you.
5

1. New Payment or Submission

Instant trigger

In Zapier“Triggers when a new payment or submission is added.”

The broadest trigger of the list: a payment on a payment page, or an entry on a survey or web form, starts the Zap. If you only build one Peggy Pay Zap, this is usually the one.

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 every new buyer or respondent into your CRM or mailing list without exporting files.
Watch out
paid orders and plain form entries arrive through the same event, so check which one your next step expects.
6

Subscription Cancelled by Customer

Instant trigger

In Zapier“Triggers when a subscription is cancelled by the customer.”

Fires when the subscriber ends the subscription themselves. That is a different signal from a cancellation you make, and keeping them apart tells you who actually decided to leave.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
alert your account manager or send an exit survey while the reason is still on the customer's mind.
Watch out
a cancellation you make from your side never reaches this Zap; it belongs to the next trigger.
7

Subscription Cancelled by You

Instant trigger

In Zapier“Triggers when a subscription is cancelled by you.”

Your own cancellations land here: the Zap runs when you, the account owner, stop a subscription from Peggy Pay. Handy when cancellations happen on your side (a closed contract, a refund agreed on the phone) and other tools must follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
revoke access in a membership tool or close the client record in your CRM.
Watch out
customers who leave on their own are not covered here, so pair it with the previous trigger.
8

Subscription Changed by You

Instant trigger

In Zapier“Triggers when a subscription is changed by you.”

Reacts when you edit an existing subscription in Peggy Pay. The plan keeps running, but something about it moved, and the rest of your stack probably needs the new version.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keep the subscription row in your reporting sheet in line with what Peggy Pay now holds.
Watch out
only changes made by you count; the name says it, and changes by a customer are not part of this event.
9

New Subscription

Instant trigger

In Zapier“Triggers when a new subscription is created.”

Fires when a recurring subscription is created on one of your pages. This is your onboarding moment: a new member, a new subscriber, a new monthly client.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
send a welcome email from your mailing tool and add the person to the right list.
Watch out
subscriptions created before the Zap was published are never picked up, so import the older ones separately.
10

Subscription Payment

Instant trigger

In Zapier“Triggers when a subscription payment has succeeded.”

Runs every time a recurring charge succeeds. Where New Subscription fires once, this one fires on each renewal, so it is the event to follow revenue month after month.

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 each renewal in your finance sheet or post it in a team channel.
Watch out
on a large subscriber base this is the trigger that eats tasks fastest; check your plan's count before switching it on.
11

Subscription Payment Failed

Instant trigger

In Zapier“Triggers when a subscription payment has failed.”

Catches a recurring charge that did not go through. The subscriber has not cancelled anything, yet the money is missing, and the sooner someone reacts, the better the odds of keeping them.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
email the subscriber to update their card and copy the case into a collections sheet.
Watch out
a failed email step does not cost a task, but it also means nobody was told, so test the Zap well.
12

Subscription Reactivated by You

Instant trigger

In Zapier“Triggers when a subscription is reactivated by you.”

Fires when you switch a stopped subscription back on. It is the reverse of a cancellation, and the tools you updated on the way out usually need undoing.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
restore the member's access and move them back to the active list in your CRM.
Watch out
only reactivations you make yourself trigger it, in line with its label.
When it breaks

When a Peggy Pay Zap breaks

Zapier lists no help article and no rate limit of its own for Peggy Pay.

What breaks is therefore general Zapier behaviour, applied to payment pages. Four cases cover most of it. When the cause is not obvious, the Zapier troubleshooting page is the next stop.

  • Past payments are never picked up

    A Zap only reacts to events that happen after you publish it. Orders and subscriptions created earlier stay out, and moving that history is a separate job.

  • The Form box decides everything

    Each trigger asks for a Form. Pick the wrong page and the Zap stays silent while payments pour in elsewhere. Check this box first when nothing arrives.

  • Bulk imports can be held back

    If a trigger suddenly sends a huge batch, after a migration for example, Zapier's flood protection can hold those runs back instead of firing them all.

  • The free plan stops at two steps

    Adding a filter or a second action to a Peggy Pay Zap makes it multi-step. On the free plan you cannot publish it until you upgrade.
Need help

Need help automating Peggy Pay with Zapier?

A person reads every message.

FAQ

Peggy Pay Zapier integration: common questions

01Is the Peggy Pay Zapier integration free?
Yes, it works on the free Zapier plan, because Zapier does not reserve Peggy Pay for paid plans. The free plan gives you 100 tasks a month and unlimited Zaps. The catch is the shape of each Zap: one trigger and one action, nothing more. The moment you want a filter or a second action, for example writing to a sheet and sending an email from the same failed payment, you need a paid plan.
02How many tasks does a Peggy Pay Zap use?
The Peggy Pay trigger itself uses none. Zapier counts a task each time an action after it succeeds, so a Zap with one action uses one task per payment, form entry or subscription event, and a Zap with three actions uses three. Actions that fail are not counted. On busy pages, Subscription Payment and New Payment or Submission are the triggers that add up fastest, so estimate your volume before you pick a plan.
03Do Peggy Pay triggers run in real time?
Yes. All 12 Peggy Pay triggers are instant: Peggy Pay reports the event to Zapier when it happens, so the Zap starts right away. The interval grid that slows polling triggers on cheaper plans, 15 minutes on Free, does not apply to them. You can spot an instant trigger by the lightning bolt Zapier shows in the editor. This is the main argument for running Peggy Pay on the free plan.
04What does it take to connect Peggy Pay to Zapier?
An existing Peggy Pay account, plus access to any page you do not own and want the Zap to watch. In Zapier, open the Apps page, click + Add connection, search for Peggy Pay, then sign in and allow access in the tab that opens. Before building the trigger, check that the account already has at least one payment page or form, since every trigger asks you to pick one. That connection is made once, then reused by every Peggy Pay step you add.
05Why would a Peggy Pay Zap never start?
Most of the time the wrong Form is selected. Every Peggy Pay trigger is tied to the page chosen in that box, so payments on any other page never reach the Zap. Second suspect: the event happened before the Zap was published, and Zapier never goes back in time. Third: the trigger does not match the case, for instance a cancellation you made yourself, which only Subscription Cancelled by You catches.
06What if the Peggy Pay operation you need is not there?
Then Zapier cannot do it for Peggy Pay today. The integration has 12 triggers and no action or search, so creating an order, editing a subscription or looking up an old payment from a Zap is not possible. The practical route is to let a Peggy Pay trigger start the Zap and do the work in another app. Anything that must change inside Peggy Pay stays a manual task in its own interface.
07Zapier, Make or n8n for Peggy Pay?
Decide on criteria rather than brand. On Zapier, Peggy Pay is a listen-only app: 12 instant triggers, no action, no search, and it runs on the free plan as long as each Zap stays at two steps. If listening to payments and pushing them elsewhere is all you need, that covers it. If you need to write back into Peggy Pay, or to branch heavily on each payment, check what each platform offers for this app before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations