PayPal Capture Payment: PayPal action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Order ID orderId	string	Required	Order ID

Sample request

{
  "orderId": "{{trigger.orderId}}"
}

Returns

{
  "id": "ORDER-123",
  "status": "COMPLETED",
  "purchase_units": [
    {
      "payments": {
        "captures": [
          {
            "id": "CAP-123",
            "amount": {
              "value": "99.99",
              "currency_code": "USD"
            },
            "status": "COMPLETED"
          }
        ]
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about PayPal Capture Payment.

What does the PayPal Capture Payment action do in PayPal?

Captures a previously-authorised payment. The standard "buyer approved + we've verified the order → capture funds" step.

What inputs does PayPal Capture Payment require?

Required: Order ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if PayPal returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does PayPal Capture Payment support batch operations?

Yes. Run PayPal Capture Payment inside a Loop node to process arrays. Tiny Command handles PayPal's rate limits automatically so you don't have to throttle manually.

More actions