Short answer: Drop the "Stripe → Get Invoice" 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 |
|---|---|---|---|
Invoice ID invoice_id | string | Required | Invoice ID. e.g. "in_abc123" |
{"invoice_id": "in_abc123"}
{"id": "in_abc","lines": {"data": [{"amount": 1999,"description": "Pro Plan"}]},"status": "paid","customer": "cus_abc","amount_due": 1999,"amount_paid": 1999,"hosted_invoice_url": "https://invoice.stripe.com/i/abc"}
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.