Pipedream Stripe → n8n
6 Pipedream Stripe actions and 6 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slug: stripe.
Actions
| Pipedream action | n8n | Fit |
|---|---|---|
| stripe-create-customer | Stripe customer → create | Check output |
| stripe-retrieve-customer | Stripe customer → get | Direct |
| stripe-search-customers | Http Request | Check output |
| stripe-create-payment-intent | Http Request | Check output |
| stripe-create-invoice | Http Request | Check output |
| stripe-create-refund | Http Request | Check output |
Triggers (event sources)
| Pipedream trigger | n8n | Fit |
|---|---|---|
| stripe-new-payment | Stripe Trigger | Direct |
| stripe-new-customer | Stripe Trigger | Direct |
| stripe-new-invoice | Stripe Trigger | Direct |
| stripe-new-subscription | Stripe Trigger | Direct |
| stripe-canceled-subscription | Stripe Trigger | Direct |
| stripe-custom-webhook-events | Stripe Trigger | Direct |
Credentials
Create a Stripe credential in n8n (type stripeApi). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.
What "Fit" means
Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.
Questions
Does n8n have a Stripe node?+
Yes. 2 of the 6 Pipedream Stripe actions listed here map to a native n8n node; 4 map to n8n's HTTP Request node with the Stripe credential.
Will my Pipedream Stripe connection move to n8n?+
No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a Stripe credential in n8n (type stripeApi) and select it on the converted nodes.
Are Pipedream Stripe triggers supported in n8n?+
6 of the 6 Pipedream Stripe event sources listed here have an n8n trigger node. The rest are rebuilt with a Schedule Trigger that polls the API, or a Webhook node.
What happens to code steps that call the Stripe API?+
Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.