n8n Stripe Integration: Advanced Payment Workflows, Webhooks, and Recurring Billing Automation

Stripe is the backbone of modern payment processing, but manual follow-ups on failed payments, subscription management, and revenue tracking eat up SMB operators' time. n8n's native Stripe node lets you automate the entire payment lifecycle: capture webhooks, retry failed charges, segment customers, and feed payment data into your dashboard—all without code.

In this guide, I'll show you how to build three production-grade workflows that solve real SMB pain: failed payment recovery, subscription onboarding automation, and daily revenue reporting. By the end, you'll have a repeatable system that scales from 10 to 10,000 customers without manual intervention.

---

Why n8n + Stripe?

The problem: Zapier + Stripe is a dead-end. Zapier's Stripe integration can't listen for custom webhooks reliably, doesn't support Stripe's full API, and charges per task. SMBs building subscription products waste 10+ hours/month on payment chasing and reporting.

The solution: n8n's Stripe node + webhook listener gives you:

• ✅ Full Stripe API access (customers, charges, subscriptions, refunds, disputes)
• ✅ Real-time webhook listening (payment_intent.succeeded, charge.failed, customer.subscription.deleted)
• ✅ Conditional logic to retry failed payments, segment customers, and trigger upsells
• ✅ Integration with Slack, email, spreadsheets, and CRMs (HubSpot, Salesforce, Airtable)
• ✅ No per-task limits; run unlimited workflows

Cost comparison:

• Zapier: $15–50/mo per step, tasks metered → $200–500/mo for a payment + CRM + email workflow
• n8n (self-hosted): $0/mo (open-source) or $25–100/mo (managed cloud)

For a 100-customer subscription business with failed payment retries + email sequences, n8n saves $150–300/mo and gives you full control.

---

Workflow 1: Failed Payment Recovery (Retry + SMB Escalation)

Use case: Customer's card declines. Instead of losing the revenue, automatically retry the charge in 3 days, send a reminder email, and escalate to your Slack if it fails again.

Setup

1. Create a Stripe webhook (one-time, in Stripe dashboard):

   • Go to Stripe → Developers → Webhooks
   • Click "Add endpoint"
   • Webhook URL: https://your-n8n-instance.com/webhook/stripe-payment-webhook
   • Events: charge.failed, charge.expired
   • Copy the signing secret

2. In n8n, create a new workflow:

   • Add a "Webhook" trigger
   • Select "POST" method
   • Path: /stripe-payment-webhook
   • Save and copy the webhook URL → paste into Stripe dashboard
   • Click "Verify signature" and paste your Stripe signing secret

Workflow Logic

Webhook (charge.failed) 
  ↓
[Parse Stripe webhook]
  ↓
{customer_id, charge_amount, retry_count}
  ↓
[Get customer details from Stripe]
  ↓
[Query your database] → does customer have a backup payment method?
  ↓
[Branch 1] YES → [Stripe: Create charge] → Retry with backup card
  └─ If success: Send email "Payment recovered"
  └─ If fail: Wait 3 days → Retry again (max 2 retries)
  └─ If fail after 2 retries: Send Slack alert + add to "at-risk" segment
↓
[Branch 2] NO → Send email "Update your payment method" + link to billing portal
  └─ Wait 7 days
  └─ Check if payment method was updated
  └─ If updated: Retry charge
  └─ If not: Cancel subscription + send Slack alert

Step-by-Step in n8n

Step 1: Add the Webhook Trigger

• Trigger type: Webhook
• HTTP method: POST
• Path: /stripe-payment-webhook

Step 2: Validate the Webhook

• Add a "Function" node to verify Stripe's signature
• Paste this code:

const crypto = require('crypto');
const signingSecret = 'whsec_...'; // from Stripe dashboard
const signature = $input.headers()['stripe-signature'];
const body = $input.body;

// Verify signature (Stripe's security requirement)
try {
  const event = JSON.parse(body);
  // Note: n8n handles this automatically with "Verify signature" toggle
  return [{ verified: true, event }];
} catch (e) {
  return [{ verified: false, error: e.message }];
}

Step 3: Extract the Customer & Charge Data

• Add a "Set" node to extract:

{
  customer_id: {{$json.data.object.customer}},
  charge_id: {{$json.data.object.id}},
  charge_amount: {{$json.data.object.amount}},
  failure_code: {{$json.data.object.failure_code}}
}

Step 4: Get Customer from Stripe

• Add "Stripe" node → action "Get customer"
• Customer ID: {{customer_id}}

Step 5: Check Database for Backup Payment

• Add "Postgres" / "MySQL" node (or your DB)
• Query: SELECT backup_card_id FROM customers WHERE stripe_customer_id = $1

Step 6: Conditional Retry

• Add "If" node: backup_card_id != null?
  • YES: Add "Stripe" node → "Create charge"
  • Customer: {{customer_id}}
  • Amount: {{charge_amount}}
  • Source: {{backup_card_id}}
  • NO: Add "Resend" node → send "Update payment" email

Step 7: Track Retry Count

• Update your database: UPDATE customers SET retry_count = retry_count + 1 WHERE stripe_customer_id = $1
• Add a "Wait" node: Wait 3 days
• Re-run the charge via a separate scheduled workflow

Step 8: Alert on Final Failure

• If retry fails 2× → Send Slack message: "⚠️ Payment failure: {customer_name} × 2 attempts. Consider reaching out."

Expected Outcome

• Recovery rate: 30–50% of failed payments recovered automatically
• Time saved: 2–3 hrs/mo on payment chasing (vs. manual email + phone follow-ups)
• Revenue impact: Example: 100 customers × $99/mo × 40% recovery rate = $3,960/mo recovered revenue

---

Workflow 2: Subscription Onboarding + Upsell Automation

Use case: New customer signs up via Stripe checkout. Automatically add them to your CRM (HubSpot, Airtable), send a welcome sequence, and tag them for upselling based on their plan tier.

Workflow Logic

Stripe Webhook: customer.subscription.created
  ↓
[Extract subscription details]
  ↓
{customer_id, plan, subscription_id}
  ↓
[Get full customer record from Stripe]
  ↓
[Branch by plan tier]
  ├─ Tier: $29/mo → Add to "Starter" segment
  ├─ Tier: $99/mo → Add to "Professional" segment
  └─ Tier: $299/mo → Add to "Enterprise" segment + notify sales team
  ↓
[Add/update in HubSpot (or Airtable)]
  ├─ Contact: name, email, plan, MRR
  ├─ Custom property: "n8n_subscription_tier"
  ├─ Custom property: "n8n_onboarded_at"
  └─ Add to "Onboarding" sequence
  ↓
[Send welcome email (Resend)]
  ├─ Subject: "Welcome to [Company]!"
  ├─ Body: Personalized onboarding guide
  ├─ CTA: "Book onboarding call" (Calendly link)
  └─ Track: email open, link clicks
  ↓
[Wait 2 days]
  ↓
[Send second email: "Quick wins you can automate today"]
  └─ Case study + upsell to next tier

Step-by-Step in n8n

Step 1: Webhook Trigger

• Event: customer.subscription.created

Step 2: Extract Subscription Data

• Set node:

{
  customer_id: {{$json.data.object.customer}},
  subscription_id: {{$json.data.object.id}},
  plan_id: {{$json.data.object.items.data[0].price.product}},
  plan_amount: {{$json.data.object.items.data[0].price.unit_amount}}
}

Step 3: Get Customer Details from Stripe

• Stripe node → "Get customer"
• Customer ID: {{customer_id}}
• Extract: email, name, created_at

Step 4: Segment by Plan Tier

• If node: plan_amount == 2900? → Starter
• Else if: plan_amount == 9900? → Professional
• Else: → Enterprise

Step 5: Add to HubSpot (or Airtable)

• HubSpot node → "Create/update contact"
  • Email: {{customer_email}}
  • First Name: {{customer_first_name}}
  • Last Name: {{customer_last_name}}
  • Custom properties:
  • n8n_subscription_tier: {{plan_tier}}
  • n8n_plan_amount: {{plan_amount}}
  • n8n_onboarded_at: {{today()}}
  • Add to list: "Onboarding"

Step 6: Send Welcome Email

• Resend node → "Send email"
  • To: {{customer_email}}
  • Subject: "Welcome to [Company]! Your automation journey starts here."
  • HTML template:

<h1>Welcome, {{customer_first_name}}!</h1>
<p>You're now on the {{plan_tier}} plan. Here's what you can do:</p>
<ul>
  <li>Automate payment follow-ups</li>
  <li>Connect to your CRM</li>
  <li>Build custom workflows</li>
</ul>
<p><a href="https://calendly.com/company/onboarding">Book your onboarding call</a></p>

Step 7: Wait & Send Upsell Email

• Wait node: 2 days
• Resend node → Send second email with case study + upsell CTA

Expected Outcome

• Activation rate: 70–80% of customers complete onboarding call within 7 days
• Upsell rate: 15–25% upgrade to next tier within 30 days
• Time saved: 2–4 hrs/mo on manual onboarding & CRM updates

---

Workflow 3: Daily Revenue Reporting Dashboard

Use case: Every morning, pull yesterday's revenue from Stripe (payments, refunds, chargebacks, MRR trends) and post to Slack or update a Google Sheet for your dashboard.

Workflow Logic

Scheduled trigger: Daily at 9 AM
  ↓
[Query Stripe API]
  ├─ Total charges (yesterday): $X
  ├─ Total refunds (yesterday): $X
  ├─ Net revenue: $X - $Y
  ├─ Subscription MRR: $X
  ├─ Chargeback count: N
  └─ Failed payment count: N
  ↓
[Calculate metrics]
  ├─ Yesterday MoM change: +X%
  ├─ Runway (if expenses = $X/mo): Y days
  ├─ Health score: A/B/C (based on chargeback + failed payment rate)
  ↓
[Post to Slack]
  └─ "📊 Daily revenue: $X net | MRR $X | Health: A"
  └─ Attach chart: Revenue trend (last 7 days)
  ↓
[Update Google Sheet]
  ├─ Add row: date, revenue, MRR, chargeback count
  └─ Update "KPI" tab with metrics

Step-by-Step in n8n

Step 1: Schedule Trigger

• Trigger type: Schedule
• Trigger time: 9 AM CT daily

Step 2: Query Stripe (Last 24 Hours)

• Stripe node → "List charges"
  • Filter: created: {gte: yesterday_start, lt: today_start}
  • Limit: 100 (use pagination if needed)

Step 3: Calculate Net Revenue

• Function node:

const charges = $input.items;
let gross = 0, refunds = 0, chargebacks = 0, failed = 0;

charges.forEach(charge => {
  if (charge.status === 'succeeded') gross += charge.amount / 100; // Stripe uses cents
  if (charge.refunded) refunds += charge.refunded_amount / 100;
  if (charge.dispute) chargebacks += 1;
  if (charge.status === 'failed') failed += 1;
});

return [{
  gross_revenue: gross,
  refunds: refunds,
  net_revenue: gross - refunds,
  chargeback_count: chargebacks,
  failed_count: failed
}];

Step 4: Get MRR from Active Subscriptions

• Stripe node → "List subscriptions"
  • Filter: status: active
• Function node:

const subs = $input.items;
let mrr = 0;
subs.forEach(sub => {
  mrr += sub.items.data[0].price.recurring.interval === 'month' 
    ? sub.items.data[0].price.unit_amount / 100 
    : 0;
});
return [{ mrr: mrr }];

Step 5: Post to Slack

• Slack node → "Send message"
  • Channel: #finance or #daily-metrics
  • Message:

📊 **Daily Revenue Report**
**Date:** {{yesterday}}
**Net Revenue:** ${{net_revenue}}
**MRR:** ${{mrr}}
**Chargebacks:** {{chargeback_count}}
**Failed Payments:** {{failed_count}}
**Health Score:** {{health_score}}

Step 6: Update Google Sheet

• Google Sheets node → "Append row"
  • Sheet: "Daily Revenue"
  • Values: [date, net_revenue, mrr, chargeback_count, failed_count]

Expected Outcome

• Daily visibility: Know your revenue + health metrics before coffee
• Early warning: Chargeback spike or payment failures caught within 24h (vs. weekly bank statements)
• Data-driven decisions: Trend visibility over 30/90 days enables better pricing/marketing decisions

---

Common Issues & Troubleshooting

Issue 1: Stripe Webhook Not Triggering

Symptoms: Workflow never fires even though charge.failed events are happening.

Fix:

1. Check Stripe → Developers → Webhooks → click your endpoint → scroll to "Events"
2. Verify events list includes charge.failed, charge.expired, etc.
3. In n8n, confirm webhook URL matches exactly (https, no trailing slashes)
4. Check n8n logs: n8n-instance → Executions → find webhook trigger → check error message
5. If error is "Signature verification failed," re-copy the signing secret from Stripe

Issue 2: Retried Charge Succeeds But Customer Gets Charged Twice

Symptoms: Customer sees two charges in Stripe dashboard.

Fix:

1. Add a database flag: BEFORE creating a charge, check if retry_attempted = true
2. Set retry_attempted = true BEFORE calling Stripe (not after)
3. This ensures only one retry per failed charge
4. Code:

UPDATE customers SET retry_attempted = true, retry_count = retry_count + 1 
WHERE stripe_customer_id = $1 AND retry_attempted = false

Issue 3: Email Sent But Subject Line Has Templating Errors

Symptoms: Email to customer shows "Hi {{customer_name}}" instead of "Hi John".

Fix:

1. Ensure your "Set" node extracts the variables BEFORE the email node uses them
2. Use the variable format: {{$json.customer_name}}
3. In Resend node, reference: To: {{customer_email}}

Issue 4: Too Many API Calls, Rate-Limited by Stripe

Symptoms: Workflow fails with "Rate limit exceeded" error.

Fix:

1. Add a "Rate limit" node between Stripe calls (set to 100 requests/sec max)
2. Use Stripe batch endpoints where possible (list operations already batch-load)
3. Cache customer details in your database instead of fetching every time

---

Best Practices

1. Always verify webhook signatures. This prevents replay attacks and ensures the event came from Stripe.
2. Idempotency is your friend. If a workflow re-runs, ensure it doesn't double-charge or double-email. Use idempotency keys in Stripe (automatically handled by n8n Stripe node).
3. Monitor your workflows. Set up Slack alerts for failed executions. A broken retry workflow is worse than no retry workflow.
4. Start small. Deploy workflow #1 (failed payment recovery) first. Measure success rate before adding workflows #2 and #3.
5. Test with Stripe test mode. Always test with Stripe test API keys (sk_test_...) before going live (sk_live_...).
6. Document your workflows. Future you (or your team) will thank you.

---

What's Next?

You now have the foundation for production-grade payment automation. Common next steps:

1. Expand to international payments: Add multi-currency support + tax calculation workflows
2. Build a dunning system: Retry failed charges with exponential backoff (3 days, 7 days, 14 days, cancel)
3. Segment for upselling: Use payment tier + engagement metrics to identify upgrade candidates
4. Integrate with your app: Sync subscription status with your user database in real-time

---

Resources

• Stripe Webhook Documentation
• n8n Stripe Node Reference
• Stripe API Reference
• n8n Scheduling Documentation

---

What payment workflow would transform your SMB? Share in the comments—I read every one.

P.S. Need help building a custom workflow? I offer a $99 audit (review your current setup + recommend improvements) and $299/mo retainer service (build + support your automation). Learn more → Schedule a discovery call.

Comments

[Mihir kanzariya]

the idempotency note needs one caveat. the auto key on the n8n Stripe node only dedupes retries of a single api call. stripe redelivers events, so two deliveries of the same charge.failed start two separate executions with two different auto-generated keys, and you get two charges. derive the key from the stripe event id yourself and the replay turns into a no-op.

related, on the signature check: n8n's webhook node hands you parsed json by default and stripe computes the signature over the raw body, so you have to switch raw body on or verification fails every time.