PaymentsReal-timeUpdated May 2026

PayPal

PayPal payment and subscription events into your stack

PayPal is the alternative-checkout-and-subscription rail that many ecommerce, donation, and SaaS businesses still need to support alongside Stripe (especially for cross-border consumer payments and donation use cases where PayPal's brand recognition matters). Five triggers cover the payment lifecycle: Order Approved (the buyer authorized the order), Payment Completed (the captured payment cleared), Payment Refunded, Subscription Created, Subscription Cancelled. Four actions cover the operational side: Create Payment, Capture Payment, Create Refund, Get Order. The integration uses PayPal's OAuth with client_id + secret from your PayPal developer dashboard. PayPal's webhook system requires per-event subscription in their developer console; the connector includes a setup helper that creates the subscriptions for you on first trigger setup. Common pattern: a PayPal Payment Completed mirrors the customer into Stripe for unified revenue reporting, files the receipt in Notion, and emails a thank-you via SendGrid, without losing the audit trail that PayPal is the actual rail.

Connect PayPal See 5 triggers

5triggers

4actions

≈ 2 minto set up

Freetier · no card

Triggers

Workflows start when PayPal does.

5 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven

Trigger live

When paypal order approved

Fires when the buyer approves an order (but before capture). For "buyer approved → trigger auto-capture" workflows.

See what it returns →

Trigger live

When paypal payment completed

Fires when a payment is captured. Payload includes amount, currency, payer info. The revenue-event hook for fulfilment, accounting sync, customer-onboarding.

See what it returns →

Trigger live

When paypal payment refunded

Fires when a refund is processed. For "revoke product access on refund", "update customer record", "log to refund tracking" workflows.

See what it returns →

Trigger live

When paypal subscription cancelled

Fires when a PayPal recurring billing agreement cancels. For churn-tracking workflows and for revoking subscription access.

See what it returns →

Trigger live

When paypal subscription created

Fires when a new subscription/billing agreement is created. For "auto-provision subscription access" customer-onboarding workflows.

See what it returns →

Actions

Do anything PayPal can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
PayPal Capture Payment	Captures a previously-authorised payment. The standard "buyer approved + we've verified the order → capture funds" step.	1 fields	View →
PayPal Create Payment	Creates a payment/order for the buyer to approve. Returns an approval URL the customer visits to authorise. For "checkout via custom flow" e-commerce workflows.	5 fields	View →
PayPal Create Refund	Refunds a payment — full or partial. For "support refund approved → execute" automation or for "fraud detection → auto-refund" workflows.	4 fields	View →
Get PayPal Order	Returns order details by ID — buyer, amount, status, payer info. The standard lookup for fulfilment workflows that need richer order context.	1 fields	View →

Recipes

Pre-built PayPal workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

PayPal → Slack alerts

AI-triage every PayPal event, ping the right channel only when it matters.

PayPal → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

PayPal → Notion database

Turn PayPal into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect PayPal once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every PayPal field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the PayPal integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect PayPal to Tiny Command?

Open the Tiny Command workflow builder, drop in a PayPal node, and click Connect. Authorize PayPal once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What PayPal triggers does Tiny Command support?

Tiny Command supports 5 real-time PayPal triggers, including "PayPal Order Approved", "PayPal Payment Completed", "PayPal Payment Refunded". Each trigger fires within seconds of the event happening in PayPal.

What PayPal actions can I run from a workflow?

4 PayPal actions are available out of the box, covering payments operations like "PayPal Capture Payment". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the PayPal integration real-time?

Yes. PayPal Order Approved and every other PayPal trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in PayPal rather than on a polling schedule.

Do I need to write code to use PayPal with Tiny Command?

No. Every PayPal trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any PayPal API endpoint directly.

How much does the PayPal integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The PayPal integration itself has no per-app surcharge.