ActionStripeUpdated June 2026

How do I list Stripe payment intents?

Short answer: You can list payment intents in Stripe by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Stripe List Payment Intents action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Payment Intents in Stripe — start free All 31 Stripe actions

List Payment Intents in Stripe — start free

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	Number of results to return (1-100)
Customer ID customer	string	Optional	Stripe customer ID — starts with 'cus_'. Find via List Customers.
Starting After starting_after	string	Optional	Cursor for pagination — pass the last payment intent ID from the previous page

Sample request

{
  "limit": "10",
  "customer": "cus_abc123",
  "starting_after": "pi_abc123"
}

Returns

{
  "data": [
    {
      "id": "pi_abc123",
      "amount": 2000,
      "object": "payment_intent",
      "status": "succeeded",
      "currency": "usd",
      "customer": "cus_abc123"
    }
  ],
  "object": "list",
  "has_more": true
}

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

Triggered by

Apps that pair well as the trigger for List Payment Intents.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Stripe

2 Google Sheets triggers

HubSpot → Stripe

18 HubSpot triggers

FAQ

Questions about List Payment Intents.

What does the List Payment Intents action do in Stripe?

Retrieves a list of payment intents, optionally filtered by customer. Useful for reconciliation and for surfacing pending payments.

What inputs does List Payment Intents require?

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

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

More actions