List Charges: Stripe 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
Limit limit	string	Optional	Limit. e.g. "10"
Customer ID customer	string	Optional	Stripe customer ID — starts with 'cus_'. Find via List Customers.

Sample request

{
  "limit": "10",
  "customer": "e.g. cus_NffrFeUfNV2Hib"
}

Returns

{
  "data": [
    {
      "id": "ch_abc",
      "amount": 1000
    }
  ],
  "has_more": false
}

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

FAQ

Questions about List Charges.

What does the List Charges action do in Stripe?

Lists Stripe charges with filters for customer, status, and date range. Used for daily reconciliation and revenue reporting.

What inputs does List Charges require?

List Charges has no required inputs. Sensible defaults are applied if you leave fields blank.

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 Stripe 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 List Charges support batch operations?

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

More actions