A PayPal connection uses a REST app made in your own PayPal business account. PayPal steps send invoices, make and capture orders, and refund captures there; PayPal charges its own fees.

Who can do this

Workspace Admins and Editors, on any plan — PayPal is not a premium connection. Viewers see the connection but cannot add or change it.

On PayPal's side, someone who can sign in to the PayPal Developer Dashboard with the business account.

Before you start

A PayPal business account. Sandbox apps work straight away with PayPal's test accounts.

Steps

In PayPal, find the app's keys:

  1. Sign in to the PayPal Developer Dashboard at developer.paypal.com with your PayPal business account.
  2. Go to Apps & Credentials.
  3. Choose Sandbox for a test app, or Live for the real one. Each has its own apps and keys.
  4. Open your REST app — or select Create App, name it Bizomate, and create it.
  5. Copy the Client ID, then show and copy the Secret.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Payments, select PayPal. It reads "Stored credential".
  3. In Connection name, type a name — for example Consulace PayPal sandbox.
  4. Paste the ID in Client ID — PayPal Developer Dashboard › Apps & Credentials › your REST app.
  5. Paste the secret in Secret — Beside the Client ID. It is hidden as you type.
  6. In Environment, choose Live (the default) or Sandbox (test) — A Sandbox app's keys work only with Sandbox, and never move real money. Choose the one the app is in.
  7. Leave Test the connection before saving ticked. Bizomate signs in to PayPal with the keys before keeping them.
  8. Select Save connection. The button reads Testing, then the dialog closes.

The toast "Connection added" says "“Consulace PayPal sandbox” is ready. Every workflow in this workspace can use it."

What happens next

  • A Sandbox connection shows the Test mode pill on Connections, on every step that uses it, and in the step's settings.
  • PayPal steps list it under Connection: Create an invoice and send it, Create an order, Capture an order, Refund a capture and Get an order. Its triggers use it too.
  • Test in the connection's panel answers "Reached PayPal · sandbox" or "Reached PayPal · live".

Good to know

  • Test mode comes from Environment. Keep a Sandbox connection for building and a Live one for the published workflow — see Steps that move money.
  • Every call signs in first. Each PayPal step asks PayPal for a sign-in with the keys, then does its work.
  • A new Secret. If you make a new secret for the app in PayPal, open the connection's panel, select Revoke and Revoke connection, then Reconnect with it.
  • Triggers make webhooks on the app when you publish — see Start a workflow from PayPal payment events.

If something goes wrong

What you see Why What to do
"Fill in Client ID." / "Fill in Secret." A box is empty. Copy it from the app in Apps & Credentials.
PayPal refused it — "PayPal refused: Client Authentication failed. Check the connection's details on Connections. Nothing was saved." The keys are wrong, or are from the other environment — Sandbox keys with Live, or the other way round. Copy both again, and choose the Environment the app is in.
"PayPal gave no access token. Check the connection's details on Connections." PayPal answered without a sign-in. Try again; if it stays, make a new secret for the app and reconnect.
"Could not reach PayPal: …" or "PayPal did not answer within 30 seconds." PayPal could not be reached. Try again in a few minutes.