PayPal n8n integrationAutomate PayPal with n8n.
Sending money should be a workflow step, not a tab you keep open. The PayPal n8n integration exposes 4 operations across 2 resources, Payout and Payout Item, plus a trigger that listens through a webhook. It fits finance and ops people who pay the same list of people every month.
Verified Trustpilot reviews · AI, automation & growth agency
What does the PayPal n8n integration actually cover?
The PayPal n8n integration connects a PayPal REST API app to your workflows. The node works on two resources: Payout, where you create a batch payout and show its details, and Payout Item, where you cancel an unclaimed item or show the details of one. The PayPal Trigger handles the other direction: PayPal calls an n8n webhook, which is a URL n8n registers when you activate the workflow, and the run starts from that call.
Three jobs come back again and again. Paying a list of contractors at the end of the month: one row per person in Google Sheets, one payout.create call, one batch sent instead of separate manual transfers. Checking what a batch contains afterwards: payout.get reads the batch details back, and the workflow writes them next to the right line. Fixing one entry: payoutItem.cancel takes back a single unclaimed item when someone was listed with the wrong address, and the other items of the batch are not part of that call.
Money in and money out rarely live in the same tool. Revenue arrives through Stripe, cross-border transfers go through Wise, and the bookkeeping side lands in Xero. n8n is the place where those four nodes share one workflow, one set of credentials and one execution log, so a payout run can be replayed and read line by line.
The node covers the Payout and Payout Item resources. For any PayPal API endpoint outside that list, the HTTP Request node calls it directly and reuses the same PayPal credential through predefined authentication, so you never manage a second Client ID for the same app.
Two things are worth knowing before you build. On payout.get, Return All chains through the pages of the API and brings everything back, while leaving it off means Limit decides how many items you get. On the trigger side, the Event Names or IDs field is required, so a PayPal Trigger with an empty event selection blocks the node instead of listening to everything.
If you are still choosing a platform, the n8n review goes through hosting, pricing model and how the editor behaves on long workflows, which matters more than the node count once a payout runs on a schedule.
How do you connect PayPal to n8n?
- 01
Create the app on the PayPal developer side
The keys do not come from the account you use to send money. Create a PayPal developer account, open the developer dashboard, then go to Apps and Credentials, REST API apps, Create app. Creating the app generates the two values n8n needs: a Client ID and a Secret. Keep the dashboard open, you copy both in the next step.
- 02
Store the credential once in n8n
In n8n, open the Credentials menu and create a PayPal credential. It asks for three things: the Client ID generated with the app, the Secret generated with it, and an Environment, where you select Live or Sandbox. A credential is created once and reused in every workflow, so this is the only screen where those keys are typed.
- 03
Point the node and the trigger at it
Add the PayPal node or the PayPal Trigger to a canvas, then pick the credential in the dropdown of the node. The same credential authenticates both, so a workflow that listens with the trigger and answers with a payout call needs one entry, not two. Pick the resource, Payout or Payout Item, and the operation list narrows to what that resource supports.
What starts a workflow from PayPal ?
PayPal Trigger is the node that starts a workflow when PayPal calls n8n. Activate the workflow: n8n gives you the webhook URL to register in PayPal, and every call becomes an execution.
What you see in n8n
Configuration notes
01Set Up the PayPal Trigger
The PayPal Trigger is a separate node from the PayPal node, and it is the one that starts a run. Version 1 asks for very little: the same PayPal credential the action node uses, picked from the same dropdown, and the events you want to hear about. Nothing else has to be configured before a first test run.
Key parameters
- Event Names or IDs: required, a multi-select. You either choose entries from the list, or you specify the IDs with an expression, which is the n8n syntax that reads a value instead of hard-coding it. Required means the node refuses to run while the field is empty, so the selection is a decision you make up front rather than a filter you add later.
02Receive Events Over the Webhook
This trigger works by webhook, meaning a URL that PayPal calls on its own. n8n registers that URL with PayPal when you activate the workflow, and each event reaches the canvas within seconds. The URL itself is produced by n8n, you do not type it. Nothing re-reads an endpoint on a timer here, so no event falls between two checks.
Key parameters
- Event Names or IDs: the selection made in the trigger is what decides which calls actually start a run.
What can the PayPal node do?
The PayPal node exposes 4 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Payout
2 operationsCreate a payout
payout.createWhat you see in n8n
Notes & use cases
One call hands PayPal a whole batch: every recipient and every amount, in a single payout.
Key parameters
- Sender Batch ID: required. A sender-specified ID number that tracks the payout in an accounting system.
- Items: add recipients one by one with Add Item, or switch to the JSON field and pass an array of individual payout items.
- Recipient Type and Receiver Value: the ID type that identifies the recipient, Email, Phone or PayPal ID, and the matching receiver value, 127 characters max.
- Amount and Currency: the value, with a currency taken from AUD, BRL, CAD, CZK, DKK, EUR or USD.
Get a payout
payout.getWhat you see in n8n
Notes & use cases
Reading a batch back gives the workflow the batch details instead of a guess about what was sent.
Key parameters
- Payout Batch ID: required, the ID of the payout for which to show details, often
{{ $json.field }}when an earlier step stored it. - Return All: on, n8n walks through the pages of the API and returns everything; off, Limit sets the maximum number of items returned.
Payout Item
2 operationsCancel a payout item
payoutItem.cancelWhat you see in n8n
Notes & use cases
Batches are rarely wrong as a whole. They go wrong on one line. This operation cancels an unclaimed payout item, and nothing else in the batch is part of the call.
Key parameters
- Payout Item ID: required, the ID of the payout item to cancel. It is the item identifier, not the batch identifier the create step was given.
Get a payout item
payoutItem.getWhat you see in n8n
Notes & use cases
Where the batch view stays high level, this one zooms in: it shows the details of a single payout item.
Key parameters
- Payout Item ID: required, the ID of the payout item for which to show details. One item per call, so a list of IDs runs through the node item by item.
Need help automating PayPal with n8n?
A person reads every message.
