PayPal

Payments Client id and secret

Create and capture orders, issue refunds, and manage subscriptions and invoices in PayPal from any Windmill script, flow or app.

Set up in 3 steps

1

Create a REST app

At developer.paypal.com, open Apps & Credentials and create a REST API app. Copy its client id and secret — switch the Sandbox and Live toggle to get the pair you want.

2

Add the resource in Windmill

Open Resources, add a resource of type paypal, and fill clientId and clientSecret.

3

Run your first script

Fork any script below and read before writing anything. There are dozens here, so search by the verb you need.

Scripts

Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.

Resource type

paypal — the shape of the credential every script on this page expects.

View raw schema →
FieldTypeRequiredWhat it is
clientIdstringYes
clientSecretstringYes

Questions

Why a pair and not a token?

The scripts exchange these two for a short-lived token on each run, so nothing expires in the resource and there is nothing to rotate by hand.

Sandbox or live?

The credentials decide, and the two environments never mix. Keep a resource for each and switch the one a flow points at.

Are my credentials stored on the hub?

Never. They live only in your own Windmill workspace, encrypted at rest.