Resources · Make integration

Plug&Paid Make integrationAutomate Plug&Paid with Make.

What if every sale, refund or canceled subscription in Plug&Paid kicked off the next step on its own? The Plug&Paid Make integration gives you 14 triggers that watch your shop. This guide links your account and walks you through a first scenario.

Try the Plug&Paid integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Plug&Paid Make integration do?

The Plug&Paid Make integration lets Make notice what happens in your Plug&Paid shop, such as a paid invoice, a shipped order or a new subscription, and pass it to the rest of your tools. You build a scenario, the automation made of modules (one brick per step), and it runs without code.

Follow up on failed payments. Start with Watch Recurring Subscription Failed and send the details to your support inbox or chat tool, so nobody finds out from an angry customer.

Keep a clean sales log. Watch Invoice Paid and Watch One Time Sale pick up each purchase, and a spreadsheet module adds a row per bundle, the single item that travels from one module to the next.

Tell buyers where their parcel is. Watch Order Tracking Number hands over each new tracking number, ready for an email module from another app.

One limit to know: Plug&Paid in Make only has triggers. It watches and reports, but it cannot create a product, refund an order or edit a customer. That work happens in the other apps of your scenario, or in Plug&Paid itself. The Make documentation also lists these modules without descriptions, so test each one with Run once before relying on it.

Before you commit, the Make review covers the tool as a whole, and Make pricing explains how operations are counted. If you are also weighing the other big platform, read n8n vs Make.

Connect

How do you connect Plug&Paid to Make?

  1. 01

    Copy your API token

    In Plug&Paid, open Settings, select the API sheet and copy the API token shown on screen. You need an active Plug&Paid account for this, since the token is what gives Make access to your data.

  2. 02

    Add a Plug&Paid module

    In your Make scenario, click the + and search for Plug&Paid, then pick one of its triggers. Click Create a connection. A connection is your Plug&Paid account linked to Make once and reused by every Plug&Paid module.

  3. 03

    Paste the token and save

    Give the connection a clear label in Connection name if you run several shops; the field is optional. Paste the token you copied, or follow the instructions Make shows on screen, and save.

First scenario

Build your first scenario with Plug&Paid

GoalWhen an invoice is paid in Plug&Paid, Make sends it to a module of another app, such as a spreadsheet or a chat tool.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the module that will start everything.

  2. 02

    Pick Watch Invoice Paid

    Search for Plug&Paid, choose Watch Invoice Paid and select the connection you created, or click Create a connection if this is your first Plug&Paid module.

  3. 03

    Add the destination

    Click the + on the right of the trigger and add a module from the app that should receive the invoice. Map the data coming from Plug&Paid into its fields by clicking the values Make offers.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time; read the bundles each module received and check the invoice data looks the way you expect.

  5. 05

    Schedule and switch on

    Click the clock on the trigger to set the schedule. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Triggers

What can start a Plug&Paid scenario?

14 modules start a scenario when something happens in Plug&Paid. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Plug&Paid as soon as it happens.

Plug&Paid1Watch Abandoned Cart

Watch Abandoned Cart

triggerIn the docs only

Catch the buyers who got as far as the cart and stopped. This trigger picks up abandoned carts in Plug&Paid so your scenario can react with a reminder or an alert to your sales team.

How it fires
scheduled, Make checks the app on the scenario's schedule and collects the carts abandoned since the previous check.
When to use it
when a cart left behind on an expensive product deserves a personal nudge rather than silence.
Watch out
the reminder leaves at the next check, not the second the buyer leaves, so plan your wording accordingly.
Plug&Paid2Watch Customers

Watch Customers

triggerIn the docs only

Get every new Plug&Paid customer into the rest of your stack without retyping. Each customer arrives as a bundle you can send to a CRM, a newsletter tool or a shared sheet.

How it fires
scheduled, Make checks the app on the scenario's schedule for customers added since the last run.
When to use it
when your customer list lives in several places and keeps drifting apart.
Watch out
the documentation gives no description of what a customer bundle contains, so run the scenario once and read it before mapping fields.
Plug&Paid3Watch Invoice Paid

Watch Invoice Paid

triggerIn the docs only

Know the moment money actually lands, not just when an order is placed. This trigger reports the invoices marked as paid in Plug&Paid, which is the safest starting point for anything touching your accounts.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when your bookkeeper wants a line in a spreadsheet for each paid invoice, or a thank-you email should only go out once payment clears.
Watch out
every module after it runs once per invoice, and each run is an operation, the unit Make counts on your plan.
Plug&Paid4Watch One Time Sale

Watch One Time Sale

triggerIn the docs only

Separate single purchases from your subscription revenue. This trigger picks up one-time sales only, which keeps your scenario focused on buyers who pay once.

How it fires
scheduled, Make checks the app on the scenario's schedule and returns the new one-time sales.
When to use it
when a one-off buyer should get a download link, a delivery notice or a place in a follow-up list that subscribers never see.
Watch out
recurring subscriptions have their own triggers further down; use Watch Recurring Subscription Created for those instead of stretching this one.
Plug&Paid5Watch Order Declined

Watch Order Declined

triggerIn the docs only

Turn a refused payment into a second chance at the sale. This trigger tells your scenario when an order in Plug&Paid is declined, so someone can reach out before the buyer gives up.

How it fires
scheduled, Make checks the app on the scenario's schedule for newly declined orders.
When to use it
when your team wants a message in its chat tool for each declined order, with enough context to call or email the buyer.
Watch out
a declined order is not a failed subscription renewal; that case belongs to Watch Recurring Subscription Failed.
Plug&Paid6Watch Order Refunded

Watch Order Refunded

triggerIn the docs only

Keep your books and your team in step when money goes back to a customer. This trigger reports refunded orders so the rest of your tools can reflect the change.

How it fires
scheduled, Make checks the app on the scenario's schedule and brings back the refunds recorded since the last check.
When to use it
when a refund should update your sales log, remove a buyer from a customer-only list or alert whoever handles returns.
Watch out
the refund itself happens in Plug&Paid; Make only reports it, since the app has no module that issues refunds.
Plug&Paid7Watch Order Shipped

Watch Order Shipped

triggerIn the docs only

Let buyers and teammates know a parcel is on its way without anyone copying order numbers by hand. This trigger fires on orders marked as shipped in Plug&Paid.

How it fires
scheduled, Make checks the app on the scenario's schedule for orders that switched to shipped.
When to use it
when shipping is done by a warehouse or a partner and your customer service needs to see it in their own tool.
Watch out
if what you need to send is the tracking number itself, Watch Order Tracking Number is the closer fit.
Plug&Paid8Watch Order Tracking Number

Watch Order Tracking Number

triggerIn the docs only

Put the tracking number in the buyer's inbox as soon as Make sees it. This trigger reacts to orders that received a tracking number in Plug&Paid.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when you want an email or text module from another app to send the buyer a shipping update that includes the number.
Watch out
run the scenario once and look at the bundle before mapping, because the documentation does not describe which order details come with the number.
Plug&Paid9Watch Product Created

Watch Product Created

triggerIn the docs only

Announce or catalog a new product the moment Make picks it up. This trigger returns products newly created in Plug&Paid, ready to feed a catalog sheet, a website or a message to your sales team.

How it fires
scheduled, Make checks the app on the scenario's schedule for products created since the previous run.
When to use it
when the people who sell your offers should hear about a launch from a scenario rather than by chance.
Watch out
this one covers new products only; for later edits, add Watch Product Updated.
Plug&Paid10Watch Product Deleted

Watch Product Deleted

triggerIn the docs only

Stop selling something elsewhere once it is gone from Plug&Paid. This trigger reports deleted products so your scenario can clean up copies in other tools.

How it fires
scheduled, Make checks the app on the scenario's schedule and collects the products removed since the last check.
When to use it
when your product list is mirrored in a spreadsheet or another store and stale entries cause confusion.
Watch out
if the next module deletes a record in another app, that step cannot be undone; test it with Run once on a dummy product first.
Plug&Paid11Watch Product Updated

Watch Product Updated

triggerIn the docs only

Keep every copy of your catalog current after an edit in Plug&Paid. This trigger returns products that changed, so the tools that repeat their details can follow along.

How it fires
scheduled, Make checks the app on the scenario's schedule for products updated since the last run.
When to use it
when a description or an offer is repeated in a sheet, a website or a sales deck and you are tired of fixing it by hand.
Watch out
the documentation does not say which changes count as an update, so edit a test product and check the result with Run once.
Plug&Paid12Watch Recurring Subscription Canceled

Watch Recurring Subscription Canceled

triggerIn the docs only

Hear about a lost subscriber while there is still time to ask why. This trigger reports recurring subscriptions canceled in Plug&Paid and hands each one to the next module.

How it fires
scheduled, Make checks the app on the scenario's schedule for new cancellations.
When to use it
when a cancellation should trigger a short survey, a note to the account owner or the removal of member access in another tool.
Watch out
keep this separate from failed payments; a canceled plan was a choice, a failed one often was not, and the message should differ.
Plug&Paid13Watch Recurring Subscription Failed

Watch Recurring Subscription Failed

triggerIn the docs only

Rescue renewals before a failed payment turns into a lost subscriber. This trigger returns recurring subscriptions whose payment failed, so your scenario can warn the customer or your team.

How it fires
scheduled, Make checks the app on the scenario's schedule and picks up the failures recorded since the previous run.
When to use it
when revenue depends on renewals and a quiet failure could turn into a lost customer.
Watch out
keep the tone helpful in the message you send, since the customer probably has not noticed the problem yet.
Plug&Paid14Watch Recurring Subscription Created

Watch Recurring Subscription Created

triggerIn the docs only

Welcome each new subscriber properly from their first payment. This trigger returns recurring subscriptions created in Plug&Paid and starts your onboarding scenario for each one.

How it fires
scheduled, Make checks the app on the scenario's schedule for subscriptions started since the last check.
When to use it
when a new member should get access to a community, a welcome sequence or a slot in your CRM.
Watch out
on the Free plan you have 2 active scenarios, so a separate scenario per subscription event fills them quickly.
Need help

Need help automating Plug&Paid with Make?

A person reads every message.

FAQ

Plug&Paid and Make: frequently asked questions

01Is the Plug&Paid Make integration free?
Yes, on the Make side. Plug&Paid is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations each month. You still need your own active Plug&Paid account, which has its own pricing.
02What is needed to connect Plug&Paid to Make?
An active Plug&Paid account with API access and its API token. In Plug&Paid, open Settings, select the API sheet and copy the token shown. In Make, add any Plug&Paid module to a scenario, click Create a connection, optionally name it, then paste the token or follow the on-screen instructions. The same connection then serves every Plug&Paid module in your scenarios, so you only do this once per account. If the token is refused, check that your Plug&Paid subscription is active.
03Do the Plug&Paid triggers in Make react in real time?
No. The Make documentation lists the 14 Plug&Paid triggers without their type, and their names point to scheduled triggers (look for the clock badge on the module): Make checks Plug&Paid on the scenario's schedule and collects what happened since the previous check. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan. Paid plans can go down to 1 minute. No instant trigger is listed for this app, so a sale or a refund reaches your other tools at the next check rather than the second it happens.
04What if a Plug&Paid module is missing in Make?
It depends on what you need. The app only offers the 14 triggers listed on this page and has no Make an API Call module, so creating products, refunding orders or editing customers from Make is not possible with this integration. Those actions stay in Plug&Paid itself. You can still use the triggers to push data into other apps that do have action modules. For a case the modules do not cover, the Make agency team can look at other options with you.
05Should Plug&Paid be automated with Make or n8n?
It depends on which platform your team already uses. On Make, Plug&Paid comes with 14 scheduled triggers and no action modules, which suits scenarios that react to sales, orders and subscriptions and send the data elsewhere. The same app may also exist as an n8n node, so compare the list of operations there before choosing. The better tool is the one whose modules match what you want to automate and that your team is comfortable building with.
Same platform

Other docs you might need on this stack.

Browse all integrations