Can I import a sanitized export without credentials?

Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own stripe and httpRequest credentials in n8n after import.

← Workflows

Stripe Payment Order Sync – Auto Retrieve Customer & Product Purchased

3 nodes · stripe, httpRequest

Engine: n8n
Nodes: 3
Trigger: scheduled/triggered
Source file: 1773_HTTP_Stripe_Sync_Webhook.json

Workflow flow

Integrations

StripeHTTPSet

100%

TRIGGER

Stripe Trigger on Payment Event

Stripe

Extract Session Information

HTTP

Filter Information

Set

3 steps · flows top to bottom, branches left to right

Browse by integration

stripe httpRequest

Browse all integrations →

Download n8n JSON Download sanitized JSON Download flow graph

Import into n8n

Download the n8n JSON file (full or sanitized).
In n8n: Workflows → Import from file.
Open each node and reconnect credentials to your accounts.
Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Stripe Payment Order Sync – Auto Retrieve Customer & Product Purchased is a free n8n workflow on OpenRuna — 3 nodes connecting stripe, httpRequest. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

"Stripe Payment Order Sync – Auto Retrieve Customer & Product Purchased" is an n8n automation built from 3 nodes spanning stripe, httpRequest. 3 nodes · stripe, httpRequest It starts from a scheduled/triggered trigger and routes data through every node in order. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

Use it as a starting template when wiring stripe, httpRequest — adjust node parameters to your accounts and record IDs.
Import "Stripe Payment Order Sync – Auto Retrieve Customer & Product Purchased" into n8n, reconnect credentials for stripe, httpRequest, and run the same automation in your own workspace.
Share it with your team as a documented reference for scheduled/triggered automations in the stripe stack.
Study how data moves from stripe to httpRequest before building your own variant.

Example output

Imported into n8n, "Stripe Payment Order Sync – Auto Retrieve Customer & Product Purchased" exposes 3 configured nodes. Trigger type: scheduled/triggered. Integrations: stripe, httpRequest. Set your credentials on the stripe node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "Stripe Payment Order Sync – Auto Retrieve Customer & Product Purchased" into Claude and ask it to explain each of the 3 nodes. Claude is good at suggesting credential mappings for stripe, httpRequest, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Stripe Payment Order Sync – Auto Retrieve Customer & Product Purchased" to your accounts — which stripe, httpRequest credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 3 nodes.

Frequently asked questions

How do I import "Stripe Payment Order Sync – Auto Retrieve Customer & Product Purchased" into n8n?: Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Stripe Payment Order Sync – Auto Retrieve Customer & Product Purchased" use?: It uses: stripe, httpRequest. The flow diagram above shows how each service connects across the 3 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?: Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own stripe and httpRequest credentials in n8n after import.
What trigger type does "Stripe Payment Order Sync – Auto Retrieve Customer & Product Purchased" use?: Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Stripe Payment Order Sync – Auto Retrieve Customer & Product Purchased" free to use?: OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for stripe, httpRequest.