Short answer: Drop the "Stripe → Delete 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 |
|---|---|---|---|
Customer ID customer_id | string | Required | Stripe customer ID — starts with 'cus_'. Find via List Customers. |
{"customer_id": "e.g. cus_NffrFeUfNV2Hib"}
{"id": "cus_abc","deleted": true}
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.