PayPal Make integrationAutomate PayPal with Make.
Can Make run your PayPal billing without a line of code? The PayPal Make integration gives you 23 modules: 4 triggers, 17 actions and 2 iterators. This guide shows sellers and subscription businesses how to link the account and build a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What does the PayPal Make integration actually do?
The PayPal Make integration links your PayPal account to Make, a no-code tool where you chain apps into a scenario (the automation you build). Each brick of that chain is a module. On the PayPal side, modules watch payments, plans and transactions, and act on billing plans, one-off payments and subscription agreements.
Subscriptions that follow your customer file. When a client pauses a contract in your CRM, Suspend an agreement puts the PayPal subscription on hold. Once the account is back in order, Reactivate an agreement restarts it. Nobody has to log into PayPal and click through each agreement.
A plan catalog that stays tidy. Watch plans spots every billing plan added to the account. Pair it with Get billing plan details to copy the plan into your product sheet, or with Deactivate plan to close an offer you no longer sell.
A two-step checkout. Create a payment (Step 1) returns an approval link for the buyer. Execute a payment (Step 2) completes the payment once the buyer has approved it, and Make carries the data from one step to the other.
What Make will not do here: PayPal has no Make an API Call module, so an operation missing from the list stays out of reach. Going live also needs a PayPal Business account. PayPal has a node on the n8n side too: see the PayPal n8n integration, and read n8n vs Make if you are still choosing. New to the editor? The Make training starts from zero.
How do you connect PayPal to Make?
- 01
Add a PayPal module
Open a scenario, click the + and search for PayPal. Pick any module, Watch plans for example, then click Create a connection. A connection is your PayPal account linked to Make once; every PayPal module reuses it afterwards.
- 02
Name it and authorize Make
Give the connection a clear name if you run more than one PayPal account, a store account and a second brand for instance. Then follow what PayPal asks: approve Make on the PayPal page, or paste the key PayPal gives you.
- 03
Save and check the account
Click Save. The module now shows the connection in its dropdown, and Make lists what it can read from the account when you fill the fields. If the plans you expect are not there, you probably linked the wrong PayPal account.
Your first scenario: document every new plan
GoalEach time someone adds a billing plan in PayPal, Make fetches everything PayPal stores about it, so the offer is documented without anyone copying it by hand.
- 01
Create the scenario
Go to the Scenarios page, create a new scenario and click the big + in the middle of the editor. That empty circle is where the first module, the trigger that starts everything, will sit.
- 02
Add Watch plans
Search for PayPal, pick Watch plans and click Create a connection. Each new billing plan comes back as a bundle, the name Make gives to one item passed from a module to the next.
- 03
Let the schedule do the checking
This trigger is scheduled: Make asks PayPal for new plans on the scenario's schedule, not the second a plan is created. Only added plans count, so editing an existing plan will not start the scenario.
- 04
Add the plan details
Click the + on the right of the trigger, choose PayPal again, then Get billing plan details. Map the plan from Watch plans, so each run reads the plan that just appeared. You now have the whole plan in hand, ready for your catalog or product sheet.
- 05
Test, schedule, switch on
Click Run once and open the bubbles above each module to read the bundles they received. When the result looks right, set the schedule on the first module (every 15 minutes by default) and turn the scenario on.
What can start a PayPal scenario?
4 modules start a scenario when something happens in PayPal. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by PayPal as soon as it happens.
New notification
Instant triggerIn Make“Triggers when a new notification is received.”
New notification starts your scenario as soon as PayPal sends Make a notification about the account. It is the only PayPal trigger that does not wait for Make to come and ask, which makes it the pick when a delay would annoy someone.
Watch custom app payments
Scheduled triggerIn Make“Triggers when a new payment is made or a payment setting is changed.”
Watch custom app payments picks up new payments tied to a custom PayPal app, and it also reacts when a payment setting changes. Each event lands as a bundle you can send to your books or a sheet.
Watch plans
Scheduled triggerIn Make“Triggers when a new plan is added.”
Watch plans notices each billing plan added to your PayPal account and hands it to the rest of the scenario. It keeps the tools around PayPal aware of every offer you publish, without anyone copying it over.
Watch transactions
Scheduled triggerIn Make“Triggers when a new transaction related to a specified agreement is made .”
Watch transactions follows one subscription agreement and starts the scenario whenever a new transaction appears on it. That gives you a precise lens on a single customer instead of the whole account.
What else can PayPal do inside a scenario?
PayPal gives you 19 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Modules index
- Activate a plan
- Bill outstanding amount
- Cancel agreement
- Create an agreement (Step 1)
- Create a payment (Step 1)
- Create a plan
- Deactivate plan
- Delete a plan
- Execute an agreement (Step 2)
- Execute a payment (Step 2)
- Get agreement transactions
- Get billing plan details
- Get plans
- Get subscription agreement details
- Reactivate an agreement
- Set outstanding agreement amounts
- Suspend an agreement
- Retrieve payment definitions
- Retrieve transactions
Activate a plan
ActionIn Make“Sets a billing plan to the ACTIVE state. Users will be able to subscribe it.”
Activate a plan switches a billing plan to the active state, and from then on customers can subscribe to it. It is how you publish an offer you prepared ahead of time.
Bill outstanding amount
ActionIn Make“Bills an outstanding or a preset amount of an agreement.”
Bill outstanding amount charges the balance still owed on a subscription agreement, or a preset amount of it. An unpaid gap becomes a real PayPal charge, triggered by your own tools.
Cancel agreement
ActionIn Make“Cancels an agreement previously approved by a user.”
Cancel agreement ends a subscription agreement the customer had approved. The subscription stops on the PayPal side, driven by whatever event you choose in Make.
Create an agreement (Step 1)
ActionIn Make“Creates a subcription agreement and returns an approval url link to obtain buyer's approval.”
Create an agreement (Step 1) prepares a subscription agreement and returns an approval link the buyer has to open. It is the first half of signing someone up to a recurring plan.
Create a payment (Step 1)
ActionIn Make“Creates a new payment order and returns an approval url link to obtain buyer's approval.”
Create a payment (Step 1) sets up a one-off payment order and hands you an approval link for the buyer. You send the link, the buyer pays on PayPal, and the scenario takes it from there.
Create a plan
ActionIn Make“Creates and activates a billing plan.”
Create a plan builds a billing plan and activates it in the same move, so subscribers can join right after the module runs. Handy when your offers live in another tool.
Deactivate plan
ActionIn Make“Sets a billing plan to the INACTIVE state. Users will not be able to subscribe to it.”
Deactivate plan sets a billing plan to inactive, which means nobody new can subscribe to it. The plan itself stays in the account, ready to come back.
Delete a plan
ActionIn Make“Permanently removes a billing plan.”
Delete a plan removes a billing plan from PayPal for good. It clears out plans that should never have existed, such as duplicates created while you were testing.
Execute an agreement (Step 2)
ActionIn Make“Executes a subscription agreement approved by a buyer after Step 1.”
Execute an agreement (Step 2) completes a subscription agreement once the buyer has approved it through the Step 1 link. This is the moment the subscription becomes real.
Execute a payment (Step 2)
ActionIn Make“Executes a payment approved by a buyer after Step 1.”
Execute a payment (Step 2) finalizes a one-off payment that the buyer approved through the link from Step 1. Until it runs, the order is only a promise.
Get agreement transactions
ActionIn Make“Returns all transactions related to a specific agreement.”
Get agreement transactions pulls the full list of transactions linked to one subscription agreement. You get the whole payment history of a customer in a single step.
Get billing plan details
ActionIn Make“Gets details about a specific billing plan.”
Get billing plan details reads everything PayPal stores about one specific billing plan. It answers the question of what a plan really contains before you act on it.
Get plans
ActionIn Make“Gets information about billing plans in a specified state.”
Get plans returns information on the billing plans that sit in a state you choose, active or inactive. Think of it as a quick inventory of your offers.
Get subscription agreement details
ActionIn Make“Returns subscription agreement details.”
Get subscription agreement details returns what PayPal knows about one subscription agreement. It gives your other tools the context they lack before they send a message or update a record.
Reactivate an agreement
ActionIn Make“Reactivates a previously suspended agreement.”
Reactivate an agreement brings a suspended subscription back to life. The customer picks up where they left off, without signing up again.
Set outstanding agreement amounts
ActionIn Make“Sets an outstanding agreement amount.”
Set outstanding agreement amounts records an amount as still owed on a subscription agreement. It prepares the balance without charging it yet.
Suspend an agreement
ActionIn Make“Suspends an agreement previously approved by a user.”
Suspend an agreement pauses a subscription the customer had approved, without ending it. Billing stops until you decide otherwise.
Retrieve payment definitions
IteratorIn Make“Enables to process each payment definition for a billing plan separately.”
Retrieve payment definitions is an iterator: it splits the payment definitions of a billing plan so each one travels through the scenario as its own bundle.
Retrieve transactions
IteratorIn Make“Enables to process transactions one at a time.”
Retrieve transactions takes a batch of transactions and feeds them one at a time to the rest of the scenario. Each transaction can then get its own treatment.
Need help automating PayPal with Make?
A person reads every message.