Short answer: Drop the "Stripe → List Invoices" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Customer ID customer | string | Optional | Customer ID. e.g. "cus_abc123" |
Subscription ID subscription | string | Optional | Subscription ID. e.g. "sub_abc123" |
Status status | options | Optional | Status. Options: All, Draft, Open, Paid, Void, Uncollectible |
Limit limit | string | Optional | Limit. e.g. "10" |
{"customer": "cus_abc123","subscription": "sub_abc123","status": "{{trigger.status}}","limit": "10"}
{"data": [{"id": "in_abc","status": "paid","customer": "cus_abc","amount_due": 1999,"amount_paid": 1999,"hosted_invoice_url": "https://invoice.stripe.com/i/abc"}],"has_more": false}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.