Short answer: Drop the "Stripe → Create Customer" 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 |
|---|---|---|---|
Email email | string | Required | Email. e.g. "customer@example.com" |
Name name | string | Optional | Name. e.g. "John Doe" |
Phone phone | string | Optional | Phone. e.g. "+1234567890" |
Description description | string | Optional | Description |
{"email": "customer@example.com","name": "John Doe","phone": "+1234567890","description": "{{trigger.description}}"}
{"id": "cus_abc123","name": "John Doe","email": "customer@example.com","object": "customer","created": 1700000000,"livemode": 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.