Resources · Zapier integration

plugnpaid Zapier integrationAutomate plugnpaid with Zapier.

The plugnpaid Zapier integration gives you 12 triggers, all instant, and no action. plugnpaid tells Zapier about sales, carts, shipments, refunds and subscriptions, and your other tools do the rest, on the free plan. Here is what it costs and what breaks.

See the 12 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the plugnpaid Zapier integration actually does

The plugnpaid Zapier integration links your plugnpaid store to Zapier, the tool that makes your apps work together without code. Each automation is called a Zap: an event in plugnpaid starts it, then steps in your other tools follow. plugnpaid brings 12 triggers to that game, all of them instant, and it works on the free plan.

Three results stores build with it. A sales feed the team actually sees: New One-Time Sale and New Recurring Subscription Sale push every purchase into a channel, a sheet or a CRM. Revenue you do not let slip: Abandoned Cart, Order Declined and Failed Recurring Charge flag the purchases that almost happened, so someone can follow up. Customers kept in the loop after paying: Order Marked as Shipped and Order Tracking Set feed the emails that tell buyers where their parcel is.

What Zapier does not do here. plugnpaid only talks: it has no action and no search step on Zapier. A Zap cannot create an order, change a customer or issue a refund in plugnpaid, and it cannot look anything up there. Every Zap therefore starts in plugnpaid and ends in another tool.

The good news hides in the trigger list: all 12 are instant, so every Zap reacts right away, even on the free plan, and the interval grid of the plans never applies. Weighing other platforms? See n8n vs Zapier and Make vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Eight words come back all over this page. Here they are in plain terms, once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap, such as a refunded order. Once the Zap is on, Zapier waits for that event.
Action
What the Zap does once started: the step that writes, sends or moves something for you. Here, it always lives in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
Instant vs polling trigger
Instant: the app calls Zapier the moment the event happens. Polling: Zapier checks the app on a timer. plugnpaid only has instant ones.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it in every other case.
Connection
Your plugnpaid account linked to Zapier once, then reused by every Zap that starts on a plugnpaid event.
Multi-step Zap
Any Zap 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 plugnpaid Zap really costs

plugnpaid is not reserved for paid plans: it works on the free one. The bill is counted in tasks, and a plugnpaid trigger never costs a single one.

  • plugnpaid trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month
  • Steps allowed on the free plan2 (one trigger, one action)

Only the actions that follow in your other apps count, one task each time one goes through; an action that fails is not counted. The free plan gives 100 tasks a month, but only Zaps of two steps: a plugnpaid trigger and one action. Add a filter or a second action and the Zap turns multi-step, which needs a paid plan. The interval grid below belongs to polling triggers, and none of the 12 plugnpaid triggers uses it.

Connect

Connect your plugnpaid account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to the Apps page and click + Add connection. You need a plugnpaid account, plus access to any store data you do not own that the Zap should read.

  2. 02

    Pick plugnpaid in the dialog

    Type plugnpaid in the search box of the dialog, select it in the results, then click Add connection. Zapier hands you over to plugnpaid so you can sign in there.

  3. 03

    Sign in and grant access

    Sign in to plugnpaid in the tab that opens and grant Zapier access to the account. The connection is stored once, and every Zap that starts on a plugnpaid event reuses it.

First Zap

Your first Zap: announce the sales that matter

GoalEach time plugnpaid records a one-time sale, keep only the ones that meet your condition and post them in the team channel.

  1. 01

    Build: choose the trigger

    Start a new Zap, choose plugnpaid as the app that starts it and New One-Time Sale as the event, then select the connection you added earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent sales of the connected store; pick a real one so the next steps are mapped on actual data.

  3. 03

    Add the filter

    Click the plus icon, add a Filter step, then set the value to check, the rule and what to compare it with. A number rule for numbers, a text rule for text, or it never passes.

  4. 04

    Add the message

    Add the action in your team chat, pick the channel, then map what the sale brought back into the message so each post says what was sold.

  5. 05

    Test, then publish

    Test the action once and read what came back, then publish the Zap to switch it on. With its filter this is a multi-step Zap, so it runs on a paid plan.

Triggers

The 12 plugnpaid triggers on Zapier

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

1

Abandoned Cart

Instant trigger

In Zapier“Triggers when a cart is abandoned.”

Starts a Zap when a shopper leaves a plugnpaid cart without paying, which gives you a second shot at a sale that was almost done.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when every lost checkout should produce a reminder email, a task for sales or a line in a recovery sheet.
Watch out
carts abandoned before the Zap was published are never picked up, so the first days only cover new ones.
2

Invoice Marked as Paid

Instant trigger

In Zapier“Triggers when an invoice is marked as paid.”

Fires once an invoice in plugnpaid gets the paid status, so the work that waits for the money can move on without anyone watching the dashboard.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when your bookkeeping sheet has to log the payment, or when a project only starts once the client has paid.
Watch out
it follows the change to paid, not the creation of the invoice, so an invoice still waiting for payment never starts this Zap.
3

Order Marked as Shipped

Instant trigger

In Zapier“Triggers when a new order is marked as shipped.”

Reacts when an order is switched to shipped in plugnpaid, the point where the parcel leaves your hands and the buyer starts waiting.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
to send a shipping notice from your email tool, or to move the order to the last column of a fulfilment board.
Watch out
tracking details are a separate event in plugnpaid, handled by Order Tracking Set; pick the one your team really fills in.
4

Order Tracking Set

Instant trigger

In Zapier“Triggers when an Order Tracking is set.”

Picks up the moment tracking is set on an order, which is the information buyers ask about most once they have paid.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when the customer should receive the tracking details by email or text without someone copying them by hand.
Watch out
the trigger test brings back the three most recent orders with tracking set, so set it on one order before building the Zap.
5

New Customer

Instant trigger

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

Runs each time plugnpaid creates a customer, which makes it the cleanest entry point for keeping a contact list in step with the store.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
to add each new buyer to your CRM, your newsletter tool or a customer sheet shared with support.
Watch out
if a second Zap also adds contacts from a sale trigger, the same person can land twice in the destination; pick one entry point.
6

New One-Time Sale

Instant trigger

In Zapier“Triggers when a new sale is made.”

Covers single purchases: each new one-time sale made through plugnpaid starts the Zap, with the details of that sale ready to map.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
to post each sale in a team channel, add a row to a revenue sheet or start the delivery of a digital product.
Watch out
subscriptions come through New Recurring Subscription Sale, so a store that sells both needs two Zaps to see every sale.
7

New Superbolts Client Subscription

Instant trigger

In Zapier“Triggers when a new Superbolts client signs up and subscribes for one of your Superbolts Billing Plans.”

Comes into play when a new Superbolts client signs up and picks one of your Superbolts Billing Plans, the moment a client relationship actually begins.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when onboarding happens elsewhere: a welcome sequence to start, a client folder to open or a kickoff task for the team.
Watch out
it only concerns Superbolts Billing Plans; other subscriptions sold in the store have their own trigger.
8

Order Declined

Instant trigger

In Zapier“Triggers when a new order is declined.”

Signals an order that did not go through because it was declined, the kind of sale that otherwise disappears without anyone noticing.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
to warn the buyer or a team member, so someone follows up on a purchase that would otherwise be lost.
Watch out
it covers orders only; a subscription payment that fails later is another event, Failed Recurring Charge.
9

Cancelled Subscription

Instant trigger

In Zapier“Triggers when a subscription is canceled.”

Tells your other tools that a subscriber has cancelled, which closes a recurring revenue line and often an access right too.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
to remove someone from a members list, tag the contact in your CRM or send a short exit survey.
Watch out
a cancellation is not a refund; money already received only shows up in Order Refunded, so keep the two Zaps apart.
10

Failed Recurring Charge

Instant trigger

In Zapier“Triggers when chare has failed.”

Fires when a subscription payment fails, the moment to act before a paying customer quietly turns into a former 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
to send the subscriber a payment reminder, or to create a task for whoever chases unpaid accounts.
Watch out
on the free plan the Zap can do one thing only; emailing the customer and alerting the team at once makes it multi-step.
11

New Recurring Subscription Sale

Instant trigger

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

Marks the creation of a new subscription sold through plugnpaid, as opposed to a single purchase, so recurring customers get their own path.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
to open an account, start an onboarding sequence or add the subscriber to a members list.
Watch out
pair it with Cancelled Subscription in a second Zap if the members list has to stay accurate in both directions.
12

Order Refunded

Instant trigger

In Zapier“Triggers when a new order is refunded.”

Fires when an order is refunded, so the money that left the store is reflected in every place where that sale was counted.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
to correct a revenue sheet, notify whoever handles the books or revoke access to a digital product.
Watch out
a large wave of refunds at once, after a bulk correction for instance, can be held back by the flood protection of Zapier.
When it breaks

When a plugnpaid Zap breaks

Zapier ties no help article to plugnpaid and lists no limit of its own for the app. What breaks is what breaks on any Zap, and four cases matter for a store.

  • No catch-up on past orders

    A Zap only reacts to what happens after you switch it on. Sales, carts and refunds from before are never sent, and moving them is a separate job.

  • Flood protection after a bulk change

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold the Zap back.

  • The filter that never passes

    Filter rules are typed: a text rule only works on text, a number rule only on numbers. Picking the wrong one is why a filter never lets anything through.

  • Nothing flows back into plugnpaid

    plugnpaid has no action and no search step on Zapier. A Zap reads its events but can never write an order, a customer or a status into the store.
Need help

Need help automating plugnpaid with Zapier?

A person reads every message.

FAQ

plugnpaid and Zapier: frequent questions

01Is the plugnpaid Zapier integration free?
Yes, it works on the free plan. plugnpaid is not reserved for paid plans, so all 12 triggers are available without paying. The free plan gives 100 tasks a month and as many Zaps as you like, with one catch: each Zap is limited to two steps, one trigger and one action. New One-Time Sale followed by a message in your team chat fits inside that limit. Add a filter, or a second action such as a row in a sheet, and the Zap becomes multi-step, which requires a paid plan.
02How many tasks does a plugnpaid Zap use?
None for the trigger, one per successful action in the apps that follow. A Zap that starts on Order Refunded and updates a sheet costs one task per refund. Add an email to the customer as a second action and the same refund costs two. An action that fails is not counted against the plan. With the 100 tasks a month of the free plan, a one-action Zap therefore handles 100 events. The count depends entirely on how many actions you stack, never on the plugnpaid side.
03Is the plugnpaid integration real-time?
Yes, for all 12 triggers. Each one is instant: plugnpaid tells Zapier the moment the sale, the refund or the cancellation happens, and the Zap starts right away on every plan, the free one included. The interval grid that slows down polling triggers, 15 minutes on Free, does not apply to any of them. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is an easy way to check. The type of a trigger is set by the app and cannot be changed from the editor.
04What does connecting plugnpaid to Zapier require?
A plugnpaid account, plus access to any store data you do not own that the Zap should read. The link is made once from the Apps page of Zapier with + Add connection: search plugnpaid, confirm, sign in to plugnpaid in the tab that opens and grant access. The connection is then reused by every Zap that starts on a plugnpaid event. Keep in mind that a Zap only sees what happens after it is published: past orders are not sent when you connect.
05Can Zapier create an order or a customer in plugnpaid?
No. plugnpaid offers no action and no search step on Zapier, only its 12 triggers. A Zap can react to a sale, a cart, a shipment, a refund or a subscription event, then act in another tool, but it can never write back into the store. Creating a customer, changing an order status or issuing a refund stays a manual job in plugnpaid. If a workflow needs that return trip, it has to be designed around this limit from the start.
06What if the plugnpaid operation you need is missing?
Then this integration cannot do it, and that is worth knowing before building. On Zapier, plugnpaid offers 12 triggers covering carts, sales, invoices, shipping, tracking, customers, Superbolts clients, declined orders, subscriptions and refunds. There is no action and no search step. If the missing piece sits in another tool, another app in the Zap may cover it. If it is an event or an action inside plugnpaid, the gap stays until the app adds that operation to Zapier.
07Zapier, Make or n8n for plugnpaid?
It depends on the workflow, not on a ranking. On Zapier, plugnpaid brings 12 instant triggers that run on the free plan, which suits a store that wants each sale, refund or cancellation sent to another tool without setup work. The criteria to weigh are the limits: no way to write into plugnpaid, no search step, two-step Zaps on the free plan and a bill counted per successful action. If one of those blocks your scenario, check what the other platforms offer for plugnpaid on those same criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations