Stripe node

Create and list customers, create and retrieve payments (Payment Intents), directly via the Stripe API. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

8 min readUpdated September 10, 2026

What this node does

Create and list customers, create and retrieve payments (Payment Intents), directly via the Stripe API.

Use Stripe as a clearly defined step in an anymize workflow.

Processes one input.
Provides one output for following steps.
Runs as a regular step in the flow.

Set up the node

01Open a workflow and add Stripe from the node catalog.
02Complete the required fields and map values from previous steps.
03Run the node with a small test record and inspect its output.
04Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Choose the required function in Action. The panel then shows the relevant settings.

Create customer
List customers
Create payment (Payment Intent)
Retrieve payment (Payment Intent)

Settings

Field	Meaning	Area
Stripe API key	Pick the workflow secret that holds your Stripe secret key (sk_live_… or sk_test_…). The key itself is never stored in the workflow.	Protected
Action	Choices: Create customer, List customers, Create payment (Payment Intent), Retrieve payment (Payment Intent)	Standard
Email	Customer's email address.	Standard
Name	Full name or business name of the customer.	Standard
Description	Free text, shown only in the Stripe dashboard.	Standard
Count (limit)	How many customers to load (1,100, default 10).	Standard
Filter by email	Optional: only load the customer with exactly this email address.	Standard
Amount in cents	Amount in the smallest currency unit, e.g. 1999 = 19.99 €.	Standard
Currency	Three-letter ISO 4217 currency code, e.g. eur or usd.	Standard
Customer ID (optional)	Optional: links the payment to an existing Stripe customer.	Standard
Payment intent ID	The ID of the payment to retrieve.	Standard
Run once per item	Off (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry.	Standard
If one item fails	"Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file.	Standard
Pause between items (milliseconds)	Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes).	Standard

Inputs and outputs

Input	Meaning	Type
Standard	Receives the complete result from the previous step.	JSON

Output	Meaning	Type
Standard	Makes the result available to the next step as JSON.	JSON

This node can process lists item by item. Error handling and the delay between items are available in advanced settings.

Example and test run

Create a new Stripe customer after they sign up in the shop: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "action": "create_customer",
  "email": "jenny.rosen@example.com",
  "name": "Jenny Rosen",
  "description": "Registriert über den Onlineshop"
}

Access and security

Before activation, review which data enters this step and what its output contains.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

No output: inspect the latest run and confirm that the previous node returned the expected fields.
Empty variable: open the previous step output and use a field name from the real test data.
List processed once: enable per-item execution in advanced settings.