Short answer: Drop the "Stripe → List Prices" 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 |
|---|---|---|---|
Product ID product | string | Optional | Stripe Product ID — starts with 'prod_'. |
Active active | options | Optional | Active. Options: All, Active only, Inactive only |
Type type | options | Optional | Type. Options: All, One-time, Recurring |
Limit limit | string | Optional | Limit. e.g. "10" |
{"product": "prod_abc123","active": "{{trigger.active}}","type": "{{trigger.type}}","limit": "10"}
{"data": [{"id": "price_abc123","type": "recurring","active": true,"object": "price","product": "prod_abc123","currency": "usd","recurring": {"interval": "month","interval_count": 1},"unit_amount": 1999}],"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.