🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home n8n Workflow
January 21, 2026

Stripe to RD Station, instant paid order events

Lisa Granqvist Partner Workflow Automation Expert

Your Stripe sales are real. Your marketing automation often isn’t. A payment comes in, but RD Station doesn’t know it happened until someone exports a CSV, updates a lead, and hopes the “customer” segment is accurate.

This Stripe RD Station automation hits marketing ops and growth teams first, honestly. But course creators and small SaaS teams feel it too, especially when follow-ups go out with the wrong message (or no message at all).

This workflow sends confirmed Stripe Checkout purchases into RD Station as Order and Payment Events, in near real time. You’ll see exactly what it does, what you need, and how to avoid the usual setup traps.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Stripe to RD Station, instant paid order events

The Problem: Paid customers don’t reach RD Station fast enough

Stripe tells you a payment succeeded, but that information usually lives in a different universe than your CRM and marketing automations. So you end up with “leads” who already bought, onboarding sequences that never trigger, and revenue attribution that is basically a guess. The worst part is the delay. If a buyer has a question or needs the login link, the first hour matters, and manual updates rarely happen that quickly. Then comes the cleanup: duplicate contacts, mismatched product names, and someone trying to reconcile what was actually purchased.

It adds up fast. Here’s where the friction shows up in real teams.

  • Someone has to check Stripe, then re-type (or copy-paste) order details into RD Station, which is slow and surprisingly error-prone.
  • Your segmentation drifts over time because purchase data arrives late, incomplete, or in a format your automations can’t reliably use.
  • Follow-up campaigns fire based on form fills or page views, not actual revenue events, so upsells and onboarding miss the mark.
  • When you finally need reporting, you’re stuck reconciling spreadsheets instead of trusting a clean event trail inside RD Station.

The Solution: Create RD Station Order & Payment Events from Stripe

This workflow listens for completed Stripe Checkout sessions and immediately turns them into structured events inside RD Station Marketing. Once Stripe confirms a checkout is paid, n8n validates the payment status, pulls the purchased line items from Stripe, and formats them into a clean “Order & Payment Event” payload. If a customer bought multiple items, it splits and maps each product, then aggregates the data so the final event matches what RD Station expects. Finally, it dispatches the event to RD Station through an HTTP request (using the RD Station community integration approach) so your automations can react right away.

The workflow starts with a Stripe Checkout trigger. It confirms the purchase is actually paid, retrieves line items, and builds a normalized order summary. Then it sends a single, well-formed event into RD Station so segmentation, attribution, and follow-ups have real revenue data behind them.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you run a course business and you get about 20 Stripe Checkout purchases a week. Manually, even a “quick” process takes about 10 minutes per order to confirm payment, copy line items, and create the right event or tag in RD Station, which is around 3 hours weekly. With this workflow, you spend maybe 10 minutes once to test a purchase, then each new order is processed automatically while you keep working. The event shows up in RD Station within minutes, ready for onboarding and upsells.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Stripe for Checkout payments and webhook events.
  • RD Station Marketing to receive Order and Payment Events.
  • Stripe API key (get it from Stripe Dashboard → Developers → API keys)

Skill level: Intermediate. You’ll connect accounts, add a Stripe webhook, and confirm event fields match what RD Station expects.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A Stripe Checkout purchase completes. Stripe hits your n8n webhook when a Checkout Session is marked completed, which kicks off the workflow immediately.

Paid orders are filtered in. The workflow validates payment status so you don’t accidentally create RD Station events for failed, pending, or incomplete payments.

Line items are retrieved and cleaned up. n8n calls Stripe to fetch the purchased products, splits items into individual records, maps the fields you care about (like name, quantity, price), then aggregates them back into a usable order summary.

An RD Station event is composed and dispatched. The workflow merges the order streams, builds the Order & Payment Event payload, and sends it to RD Station through an HTTP request so your automations can trigger right away.

You can easily modify which product fields get sent to RD Station, then route VIP purchases into different automations based on cart value or SKU. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Stripe Trigger

This workflow starts when Stripe completes a Checkout Session and expands the event payload into individual items.

  1. Add the Stripe Checkout Trigger node and set Events to checkout.session.completed.
  2. Credential Required: Connect your stripeApi credentials in Stripe Checkout Trigger.
  3. Add Expand Items List and set Field To Split Out to data.
  4. Verify the flow connects Stripe Checkout TriggerExpand Items List.
Tip: Keep the Flowpast Branding sticky note for documentation; it doesn’t affect execution.

Step 2: Connect Stripe Data Retrieval and Validation

This step filters for paid orders and pulls the line item details from Stripe.

  1. In Validate Paid Orders, add two conditions: payment_status equals paid using {{ $json.payment_status }}, and amount_total greater than 0 using {{ $json.amount_total }}.
  2. Connect Expand Items ListValidate Paid Orders.
  3. Add Retrieve Line Items and set URL to =https://api.stripe.com/v1/payment_intents/{{ $json.payment_intent }}/amount_details_line_items.
  4. Credential Required: Connect your stripeApi credentials in Retrieve Line Items.
  5. Confirm parallel execution: Validate Paid Orders outputs to both Combine Order Streams and Retrieve Line Items in parallel.
⚠️ Common Pitfall: If the Stripe API URL expression is mistyped, line items will not return and downstream aggregation will be empty.

Step 3: Process and Aggregate Line Items

Split out product details, map them into the required fields, and aggregate them into a line_items array.

  1. Add Separate Products and set Field To Split Out to data.
  2. Configure Map Item Fields with assignments: product_id = {{ $json.product_code }}, product_title = {{ $json.product_name }}, price = {{ $json.unit_cost/100 }}, quantity = {{ $json.quantity }}, variant_id = {{ $json.product_code }}, and sku = {{ $json.product_code }}.
  3. Set Aggregate Item Data with Aggregate = aggregateAllItemData and Destination Field Name = line_items.
  4. Connect Retrieve Line ItemsSeparate ProductsMap Item FieldsAggregate Item Data.

Step 4: Merge Order Streams and Build the Event Payload

This step combines the original order data with the aggregated line items and formats the payload for RD Station.

  1. Configure Combine Order Streams with Mode = combine and Combine By = combineByPosition.
  2. Connect Validate Paid Orders to input 1 and Aggregate Item Data to input 2 of Combine Order Streams.
  3. In Compose Event Payload, set fields: currency = {{ $json.currency?.toUpperCase() }}, identifier = {{ $json.payment_intent }}, price = {{ $json.amount_total/100 }}, shipping_price = {{ $json.shipping_cost/100 }}, total_items = {{ $json.line_items.length || 0 }}, line_items = {{ $json.line_items }}, and email = {{ $json.customer_details?.email }}.
  4. Connect Combine Order StreamsCompose Event Payload.

Step 5: Configure the RD Station Event Dispatch

Send the assembled order data to RD Station as an ecommerce order paid event.

  1. Configure Dispatch RD Event with URL = https://api.rd.services/platform/events and Method = POST.
  2. Enable Send Body, Send Query, and Send Headers.
  3. Set body parameters: event_type = ECOMMERCE_ORDER_PAID, event_family = CDP, and payload = {{ $json }}.
  4. Set query parameters: event_type = ECOMMERCE_ORDER_PAID.
  5. Set headers: accept = application/json and content-type = application/json.
  6. Credential Required: Connect your rdStationMarketingOAuth2Api credentials in Dispatch RD Event.
  7. Connect Compose Event PayloadDispatch RD Event.

Step 6: Test and Activate Your Workflow

Validate that paid orders create a correctly formatted event payload and that RD Station receives the event.

  1. Click Execute Workflow and trigger a test Checkout Session in Stripe.
  2. Confirm Validate Paid Orders passes only paid orders with amount_total > 0.
  3. Verify Compose Event Payload outputs fields like currency, identifier, and line_items with expected values.
  4. Check Dispatch RD Event for a successful HTTP response from RD Station.
  5. Toggle the workflow to Active to enable real-time processing.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Stripe webhook signing secrets and API keys get rotated more often than you think. If events stop arriving, check Stripe Dashboard → Developers → Webhooks and confirm the endpoint and secret match n8n.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • RD Station event payload fields need to match what your automations expect. If your segmentation is off, inspect the outgoing payload in the “Compose Event Payload” step and align naming before you build campaigns on top of it.

Frequently Asked Questions

How long does it take to set up this Stripe RD Station automation?

About 45 minutes if you already have your Stripe webhook and RD Station credentials ready.

Do I need coding skills to automate Stripe purchases into RD Station events?

No. You will connect accounts, paste keys, and test a sample checkout. The only “technical” part is copying the n8n webhook URL into Stripe.

Is n8n free to use for this Stripe RD Station workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Stripe costs (standard processing fees) and RD Station plan limits based on your account.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this Stripe RD Station workflow for different products or tags?

Yes, and you probably should. You can adjust the “Map Item Fields” and “Compose Event Payload” steps to include SKUs, coupon codes, or metadata from Stripe Checkout. Common tweaks include routing high-ticket orders to a VIP automation, mapping product IDs to friendly names, and sending customer email or name fields when you capture them at checkout.

Why is my Stripe connection failing in this workflow?

Usually it’s an expired or incorrect Stripe API key in the Stripe trigger or the “Retrieve Line Items” request. Check the credentials in n8n first, then confirm the webhook is firing in Stripe’s Webhooks dashboard. If Stripe is sending events but n8n isn’t receiving them, it’s often a wrong webhook URL or a network/security issue on your host.

How many orders can this Stripe RD Station automation handle?

A lot, as long as your n8n hosting matches your volume.

Is this Stripe RD Station automation better than using Zapier or Make?

For this specific use case, often yes. This workflow does multi-step item handling (split, map, aggregate, then merge) before it sends a single clean event to RD Station, and that kind of shaping gets expensive or awkward in simpler tools. n8n also gives you more control over what counts as “paid” and what should be ignored, so you don’t pollute your CRM with incomplete orders. The catch is hosting: this template uses a community node approach, so self-hosting is typically the practical route. If you want the simplest possible setup and your needs are basic, Zapier or Make can still work. Talk to an automation expert if you’re not sure which fits.

Once purchase events land in RD Station automatically, your campaigns stop guessing and start reacting to revenue. Set it up, test a checkout, and you’re done.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Launch login modal Launch register modal