How to Set Up Stripe Renewal Due in 30 Days → Auto Email Sequence + Slack in n8n
Every month, subscriptions renew whether you're watching or not. A customer's card expires, a renewal fires at a price they forgot they agreed to, or a high-value account churns silently because nobod
Every month, subscriptions renew whether you're watching or not. A customer's card expires, a renewal fires at a price they forgot they agreed to, or a high-value account churns silently because nobody told them it was coming. For a SaaS or agency running on Stripe, the 30-day window before a renewal is the single most valuable moment in the customer lifecycle — it's when you can prevent involuntary churn, upsell, or simply build trust with a heads-up. Most teams do nothing with it, because doing it by hand means living inside the Stripe dashboard. This article shows you how to automate the entire 30-day renewal runway in n8n: a proactive notice, a follow-up reminder, and a Slack summary for your team — all firing on their own.
The problem: renewals happen in the dark
Stripe handles the billing mechanics perfectly. What it doesn't do is orchestrate communication around the renewal. There's no built-in "email the customer 30 days before their next invoice, then again at 7 days, then tell my team in Slack." You either pay for a retention SaaS that does one narrow thing, or you build a fragile cron script that nobody maintains.
The cost of ignoring this window is concrete. Involuntary churn — failed payments from expired or maxed-out cards — accounts for 20–40% of total churn in most subscription businesses. A customer who gets zero warning before a $299 annual renewal is far more likely to dispute the charge or churn on the spot. And your ops or success team, flying blind, can't intervene on the accounts that actually matter. The information exists inside Stripe; it's just trapped there, invisible until the charge already went through.
The solution: a scheduled renewal pipeline in n8n
The fix is a single n8n workflow that runs every day, asks Stripe "which subscriptions renew in exactly 30 days?", and then branches into three actions: a renewal notice email to the customer, a queued reminder for the 7-day mark, and a Slack summary to your team channel. n8n is the right tool here because it speaks native Stripe, handles the date math, loops over multiple customers in one run, and connects to your email provider and Slack without a line of glue code.
The logical flow looks like this: a Schedule Trigger fires daily → an HTTP Request (or Stripe node) pulls upcoming subscriptions → a Code/Filter node keeps only those renewing in 30 days → an Email node sends the notice → a Slack node posts the summary. The reminder is a second scheduled branch that catches the same subscriptions at 7 days out. It's roughly eight nodes, and it replaces a job nobody wanted to own.
Step-by-step setup in n8n
1. Add the Schedule Trigger. Drop a Schedule Trigger node and set it to run once daily — 8:00 AM in your business timezone is a sensible default. Set the interval to "Days" with a value of 1. This node is the heartbeat; everything downstream runs off it.
2. Query Stripe for renewals. Use an HTTP Request node (more flexible than the native Stripe node for this) pointed at GET https://api.stripe.com/v1/subscriptions with status=active. Set Authentication to "Predefined Credential Type" → Stripe API, so your secret key never sits in plaintext. Add query parameters to expand customer data: expand[]=data.customer. The response gives you each subscription's current_period_end as a Unix timestamp — the exact moment the next renewal charges.
3. Filter to the 30-day window. Add a Code node. Compute today's date, add 30 days, and keep only subscriptions whose current_period_end falls on that target day. Something like:
const target = Math.floor(Date.now()/1000) + 30*86400;
return items.filter(i => {
const end = i.json.current_period_end;
return end >= target - 43200 && end <= target + 43200;
});
The 12-hour (43200s) buffer on each side ensures you catch the renewal exactly once, regardless of when in the day it was created. This is the single most important node to get right — a loose window sends duplicate emails, a tight one misses customers entirely.
4. Send the renewal notice. Wire the filtered output into an Email node (Gmail, SMTP, SendGrid — whatever you run). Because n8n passes each subscription as a separate item, the node loops automatically, sending one personalized email per customer. Map the recipient to {{ $json.customer.email }} and pull the plan name and amount into the body: "Your subscription renews on {{ renewal date }} for {{ amount }}." Give them a link to update their payment method — this alone prevents a chunk of involuntary churn.
5. Post the Slack summary. Before the emails fan out, add a Slack node set to "Send Message." To get a single digest instead of one Slack ping per customer, place an Aggregate node ahead of it to roll all items into one list, then format the message: "📅 12 subscriptions renew in 30 days — total MRR at risk: $4,200." Post it to a channel like #renewals so success and finance both see it. Use the Slack node's credential OAuth flow rather than a raw webhook for reliability.
6. Queue the 7-day reminder. Duplicate the trigger-query-filter chain into a second branch, but change the Code node's offset to 7*86400. This catches the same subscriptions a week out with a firmer nudge: "Your renewal is in 7 days." Keeping it as a separate scheduled branch — rather than a delayed wait inside the first — means a workflow restart never loses a pending reminder.
Benefits: what this actually changes
Once live, the workflow turns a blind spot into a system. Customers get warned before every charge, which cuts disputes and chargebacks and gives at-risk accounts a chance to update a failing card before it fails. Your team gets a daily Slack digest that turns "we found out after they churned" into "we knew 30 days out and reached out." And it runs at zero marginal cost — no per-seat retention SaaS, no maintenance window. One n8n workflow scales from 10 subscriptions to 10,000 without changing a node.
The compounding win is data. Because every renewal now flows through one pipeline, you can later branch it: high-value accounts route to a human, annual plans get a different message than monthly, failed-payment retries trigger their own sequence. You've built the rail; adding cars is trivial.
Common pitfalls to avoid
Duplicate sends. The most frequent bug. If your filter window is too wide or the workflow runs more than once a day, customers get the same email twice. Keep the Schedule Trigger to once daily and use the tight 12-hour buffer above. For extra safety, log sent subscription IDs to a database or a Set node and skip anything already processed.
Timezone drift. Stripe returns timestamps in UTC. If your Schedule Trigger and date math don't agree on timezone, you'll fire a day early or late. Do all comparisons in Unix seconds (as shown) and you sidestep the problem entirely — timestamps have no timezone.
Pagination. Stripe returns a maximum of 100 subscriptions per request. If you have more, the API response includes has_more: true, and a naive single call silently drops everyone after the first hundred. Add a loop that follows the starting_after cursor until has_more is false, or use n8n's built-in pagination options on the HTTP Request node.
Rate limits and API keys. Use your Stripe restricted key with read-only subscription access, not your full secret key — the workflow only needs to read. And if you're on Stripe's live mode with thousands of subscriptions, space out the customer-expand calls so you don't trip the rate limiter mid-run.
Silent failures. If the email provider rejects a send or Slack times out, n8n will error on that item. Turn on "Continue On Fail" for the Email node so one bad address doesn't halt the whole batch, and add an error-workflow that pings you when a run fails — so the automation you built to prevent silent churn doesn't itself fail silently.
Wire these six nodes together, test with a single subscription in Stripe test mode, then flip to live. In under an hour you've closed the most expensive blind spot in your billing stack.
Ja construimos isso pra voce
Nao comece do zero. O Stripe Renewal Due in 30 Days → Auto Email Sequence + Slack e um workflow n8n pronto para instalar — conecta suas ferramentas em minutos, sem codigo.
Instalar por $29 →
