List Customers: 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"
Email email	string	Optional	The email address. Used as the recipient or identifier depending on context.

Sample request

{
  "limit": "10",
  "email": "e.g. user@example.com"
}

Returns

{
  "data": [
    {
      "id": "cus_abc",
      "email": "user@example.com"
    }
  ],
  "has_more": false
}

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

FAQ

Questions about List Customers.

What does the List Customers action do in Stripe?

Lists Stripe customers with filters for email and creation date. Used for CRM sync or for bulk operations like sending updates to all customers.

What inputs does List Customers require?

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

Yes. Run List Customers 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