Short answer: Drop the "Stripe → Get Product" 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_id | string | Required | Product ID. e.g. "prod_abc123" |
{"product_id": "prod_abc123"}
{"id": "prod_abc123","name": "Pro Plan","active": true,"images": [],"object": "product","created": 1700000000,"description": "Monthly pro subscription","default_price": "price_abc123"}
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.