DEV Community: FlowYantra

How to Run AI Workflows Locally with n8n + Ollama (No API Costs)

FlowYantra — Sat, 21 Mar 2026 05:19:27 +0000

Every AI workflow tutorial assumes you are paying OpenAI $0.03 per 1K tokens. But what if you could run the same workflows locally, with zero API costs, and keep your data on your own machine?

You can. Here is how to connect n8n with Ollama to build local AI workflows.

What You Need

n8n (self-hosted or desktop) -- install guide
Ollama -- local LLM runner, dead simple to install
A machine with at least 8GB RAM (16GB recommended for larger models)

That is it. No API keys, no billing dashboards, no usage limits.

Step 1: Install Ollama

Head to ollama.com and download the installer for your OS. On Mac and Windows it is a standard installer. On Linux:

curl -fsSL https://ollama.com/install.sh | sh

Verify it is running:

ollama --version

Ollama runs a local API server on http://localhost:11434 by default. This is what n8n will talk to.

Step 2: Pull a Model

Ollama supports dozens of open-source models. For workflow automation, I recommend starting with one of these:

# Fast and lightweight (3.8B params) -- good for summarization and extraction
ollama pull phi3

# More capable (7B params) -- good for content generation
ollama pull mistral

phi3 runs comfortably on 8GB RAM. mistral needs about 8GB free and runs better with 16GB.

Test it works:

ollama run phi3 "Summarize this in one sentence: n8n is an open-source workflow automation tool."

You should see a response in a few seconds. Model is loaded and ready.

Step 3: Connect n8n to Ollama

Ollama exposes an OpenAI-compatible API. In n8n, you connect to it using the HTTP Request node -- no special plugin needed.

The endpoint you will call:

POST http://localhost:11434/api/generate

The request body:

{
  "model": "phi3",
  "prompt": "Your prompt here",
  "stream": false
}

Setting stream: false is important -- it makes Ollama return the complete response in one JSON object instead of streaming chunks.

The response looks like:

{
  "model": "phi3",
  "response": "The generated text appears here...",
  "done": true
}

You grab {{ $json.response }} in the next node and use it however you want.

Step 4: Build a Text Summarizer Workflow

Let us build a practical example: a webhook that accepts text and returns an AI-generated summary.

The workflow (4 nodes):

1. Webhook node (trigger)

Method: POST
Path: /summarize
This receives the text to summarize

2. HTTP Request node (Ollama call)

Method: POST
URL: http://localhost:11434/api/generate
Body (JSON):

{
  "model": "phi3",
  "prompt": "Summarize the following text in 2-3 sentences. Be concise and capture the key points.\n\nText: {{ $json.body.text }}",
  "stream": false
}

3. Set node (format response)

Set a field summary to {{ $json.response }}

4. Respond to Webhook node

Returns the summary to the caller

Test it:

curl -X POST http://localhost:5678/webhook/summarize \
  -H "Content-Type: application/json" \
  -d '{"text": "n8n is a workflow automation tool that allows users to connect various services and automate tasks. It supports over 400 integrations and can be self-hosted for complete data privacy. Unlike SaaS alternatives, n8n has no per-task pricing, making it cost-effective for high-volume automation."}'

You get back a clean summary, generated locally, with zero API costs.

Going Further: Chat Completions API

Ollama also supports the OpenAI-compatible chat completions endpoint:

POST http://localhost:11434/v1/chat/completions

This means you can use n8n's built-in OpenAI node by pointing it at http://localhost:11434/v1 as a custom base URL. Same node, same interface, but the model runs on your hardware.

When to Use Local vs Cloud AI

Use Case	Local (Ollama)	Cloud (OpenAI/Claude)
Summarization	Great	Overkill
Text extraction	Great	Overkill
Content generation	Good (7B+ models)	Better quality
Complex reasoning	Limited	Much better
Data privacy	Full control	Data leaves your machine
Cost at scale	Free	Adds up fast

For most automation tasks -- summarizing, extracting, classifying, reformatting -- a local 7B model is more than enough. Save the cloud APIs for tasks that genuinely need GPT-4 level reasoning.

What We Are Building

At FlowYantra, we are working on n8n templates that use local LLMs for privacy-first automation. If you need a cloud-based AI workflow right now, check out our Blog to Social AI template -- it uses OpenAI today but the architecture is model-agnostic, so swapping to Ollama is straightforward.

All our templates (free and paid) are on our Gumroad store.

Local AI is not the future. It is already here. And with n8n, it takes about 20 minutes to set up.

Why I Stopped Using Zapier and Switched to n8n (And Saved $2,400/Year)

FlowYantra — Sat, 21 Mar 2026 05:14:02 +0000

Last year, I was paying Zapier $49 per month. That is $588 a year just for the Pro plan -- and I was constantly hitting limits.

Today I run more workflows, handle more volume, and pay exactly $0 for the workflow engine. Here is what happened.

The Zapier Problem

Zapier is great for getting started. You connect two apps, set a trigger, and it just works. But the moment you try to build anything real, you hit walls:

Per-task pricing eats you alive. Zapier Pro gives you 750 tasks per month. Sounds like a lot until you realize a single multi-step Zap can consume 5+ tasks per run. My Stripe notification workflow alone was burning through 200 tasks a month.

Multi-step Zaps cost more. Want more than 2 steps? That is the Pro plan minimum. Want paths, filters, and formatters? Better upgrade again.

No code when you need it. Zapier has "Code by Zapier" but it is sandboxed, limited, and painful for anything beyond string manipulation.

Data leaves your control. Every piece of data flows through Zapier's servers. For a business handling payment data, customer PII, and API keys, that is a real concern.

I did the math: to run all my workflows comfortably, I would need the Teams plan at $69/month ($828/year) or higher. And that number only goes up as the business grows.

The Switch to n8n

I had heard about n8n but assumed it was some hobbyist tool. I was wrong.

n8n is an open-source workflow automation platform that you can self-host for free or use their cloud starting at around $20/month. It has 400+ integrations, a visual workflow builder, and -- crucially -- no per-task pricing.

Let me break down the cost comparison:

	Zapier Pro	n8n Self-Hosted	n8n Cloud (Starter)
Monthly cost	$49	$0	~$20
Annual cost	$588	$0 (+ server ~$5-10/mo)	~$240
Tasks/month	750	Unlimited	2,500+
Multi-step workflows	Extra cost	Included	Included
Code nodes	Limited	Full Node.js/Python	Full Node.js/Python
Self-host option	No	Yes	N/A (cloud)

Even with n8n Cloud, I am saving roughly $350 a year. Self-hosted on a $5 VPS? That is over $2,400 saved over 4 years compared to Zapier Teams pricing.

What Actually Got Better

Cost savings are nice, but the real wins were functional:

Unlimited workflows, no anxiety

With Zapier, every new automation made me check my task count. With n8n, I build whatever I want. Need a workflow that runs every minute? Go for it. No meter ticking.

Real code when you need it

n8n has a Function node where you can write actual JavaScript (or Python). Not some sandboxed snippet -- real code with npm packages. When I needed to parse a complex webhook payload from Stripe, I wrote 15 lines of JS and moved on. In Zapier, I would have needed 3 Formatter steps and a prayer.

Self-hosted data privacy

My Stripe webhooks, customer emails, and payment data never leave my server. For anyone handling PII or financial data, this is not optional -- it is a requirement.

Community workflows

n8n has a massive template library and an active community. When I needed a workflow pattern, chances are someone had already built it and shared it.

Error handling that actually works

n8n lets you add error workflows, retry logic, and conditional branching at every node. Zapier's error handling is basically "we will email you when something breaks."

The Migration Was Easier Than Expected

I migrated 12 Zapier workflows to n8n over a weekend. The hardest part was re-authenticating OAuth connections. The actual workflow logic was faster to rebuild in n8n because the visual builder is more powerful.

My approach:

List all active Zaps
Rebuild them one by one in n8n (start with the simplest)
Run both in parallel for a week
Turn off Zapier

Total migration time: about 8 hours spread over 2 days.

Who Should NOT Switch

Being honest: n8n is not for everyone.

If you have 2-3 simple two-step Zaps, Zapier's free tier is fine. Do not over-engineer it.
If you have zero interest in managing a server, n8n Cloud is the middle ground, but Zapier is more hands-off.
If your company mandates a specific vendor, you may not have a choice.

But if you are a solopreneur, a small team, or a developer who wants control over your automation stack, n8n is the clear winner.

What We Built With n8n

At FlowYantra, we now build all our automation templates on n8n. Two of our most popular:

Stripe Payment Notifier -- real-time payment alerts to Slack, Email, and Discord
Blog to Social AI -- AI-powered content repurposing from blog to social media

Both are available as free starters on GitHub and as full production templates on our Gumroad store.

If you are tired of watching your Zapier bill climb, give n8n a serious look. Your wallet will thank you.

5 n8n Workflows Every Solopreneur Needs in 2026

FlowYantra — Sat, 21 Mar 2026 05:13:53 +0000

You are wearing every hat in your business. Marketing, support, billing, ops -- all you. Every minute you spend copy-pasting data between apps is a minute you are not building your product.

Here are five n8n workflows that buy back hours of your week, starting today.

1. Instant Payment Alerts (Stripe to Slack/Email/Discord)

The problem: a customer pays you, and you find out... whenever you happen to check Stripe.

The fix: a webhook-triggered workflow that catches every Stripe event -- successful charges, failed payments, subscription changes, refunds -- and routes a formatted notification to Slack, email, or Discord within seconds.

Why it matters: you respond to failed payments before the customer even notices. You celebrate wins in real time. Your team (even if that team is just you) stays in the loop without checking dashboards.

We built a production-ready version of this exact workflow:

Free starter: stripe-payment-notifier-n8n on GitHub
Full template with multi-channel routing and retry logic: FlowYantra Gumroad Store

2. Blog-to-Social Content Repurposing

The problem: you spend 3 hours writing a blog post, then another hour manually creating LinkedIn posts, tweets, and email snippets from it.

The fix: an n8n workflow that monitors your RSS feed (or CMS webhook), sends the content through an AI node for repurposing, and posts to multiple platforms automatically.

One blog post becomes 5+ pieces of content without you touching a keyboard.

We have a full template for this too:

Free starter: blog-to-social-ai-n8n on GitHub
Full template with scheduling and tone control: FlowYantra Gumroad Store

3. Uptime Monitoring with Instant Alerts

The problem: your site goes down at 2 AM. You find out at 9 AM from an angry customer email.

The fix: a simple n8n workflow using the Cron node to ping your URLs every 5 minutes via the HTTP Request node. If the response code is not 200, it fires a notification to Slack or sends you an SMS via Twilio.

Here is the basic structure:

Cron (every 5 min) -> HTTP Request (GET your-site.com) -> IF (status != 200) -> Slack/Email/SMS

Add a Function node to track consecutive failures so you do not get spammed by a single timeout. Three failures in a row? That is a real alert.

Total setup time: about 15 minutes. Cost: zero (if you self-host n8n).

4. Invoice Automation

The problem: you are manually creating invoices in Google Docs or some PDF tool, then emailing them. It takes 20 minutes per client.

The fix: an n8n workflow triggered by a new row in Google Sheets (or Airtable, or a form submission). It pulls client details, generates a PDF invoice using an HTML to PDF service or a template in Google Docs, and emails it to the client -- all automatically.

The flow looks like:

Webhook/Sheet Trigger -> Fetch Client Data -> Generate PDF (via Gotenberg or Google Docs API) -> Send Email with Attachment

Bonus: add a node that logs the invoice to your accounting spreadsheet. Now your books stay clean without extra effort.

5. Customer Onboarding Email Sequences

The problem: a new customer signs up, and you either forget to send the welcome email or spend 10 minutes doing it manually.

The fix: a webhook-triggered workflow that fires when a new user is created (from Stripe, your app database, or a form). It sends a welcome email immediately, waits 2 days using the Wait node, sends a tips email, waits 5 more days, and sends a feedback request.

Webhook (new user) -> Send Welcome Email -> Wait 2 days -> Send Tips Email -> Wait 5 days -> Send Feedback Email

No email marketing tool needed. No monthly fees. Just n8n and your SMTP server (or Gmail node).

The Common Thread

All five workflows share the same idea: detect an event, process it, take action -- without you in the middle.

n8n makes this dead simple because:

You can self-host it (no per-task pricing)
The visual builder means you do not need to be a developer
Code nodes let you handle edge cases when the visual builder is not enough
400+ integrations cover almost every SaaS tool you are already using

Get Started

We build production-ready n8n templates at FlowYantra so you do not have to start from scratch. Each template comes with documentation, error handling, and real-world testing.

Stop doing repetitive work. Automate it.

How to Automatically Turn Blog Posts into Social Media Content with n8n and OpenAI (Free Template)

FlowYantra — Sat, 21 Mar 2026 02:30:28 +0000

I publish a blog post. Then I spend the next two hours:

Rewriting it as a Twitter thread (5 tweets, each under 280 chars)
Adapting it to LinkedIn tone (professional, paragraph breaks, no hashtag spam)
Compressing it to an Instagram caption (more emoji, 20+ hashtags)
Adding a question hook for Facebook
Writing a newsletter snippet to drive click-throughs

Same content. Five rewrites. 2+ hours. Every single post.

So I automated it with n8n and OpenAI. Now each new blog post triggers a workflow that generates all 5 social posts in about 30 seconds, delivers them to Slack for review, and logs them to Google Sheets. I copy-paste and publish.

Here's exactly how it works, and you can grab the free template at the bottom.

The Problem with Manual Content Repurposing

Content repurposing is one of those tasks that feels optional until you look at the math.

If you publish 4 blog posts a month and spend 2 hours per post on social repurposing, that's 8 hours a month – 96 hours a year – on mechanical rewriting work. That's more than two full working weeks, spent on a task that doesn't require your expertise.

The real cost isn't even the time. It's the inconsistency. When you're tired or rushed, the LinkedIn post is weak. The Twitter thread is just the intro paragraph split into 280-char chunks. The Instagram caption is the LinkedIn post with emojis thrown in. The content gets published but it doesn't perform.

AI handles this better than a tired human does at 11 PM before scheduling posts.

How the Workflow Works

The n8n workflow is a linear pipeline: detect new post → fetch content → generate → deliver.

The pipeline:

RSS Trigger (every 30 min) detects new blog posts
Validate Input – catches empty titles/URLs early
Fetch Blog Content – HTTP Request gets full page HTML
Extract Article Text – strips HTML, targets article/main tags
OpenAI GPT-4o generates social posts (with AI fallback on error)
Delivers to Slack, logs to Google Sheets, optionally queues to Buffer

Let me walk through each stage.

Stage 1: Detecting New Blog Posts

The workflow starts with n8n's RSS Feed Trigger node. You point it at your blog's RSS feed URL (usually yourblog.com/feed or yourblog.com/rss.xml) and set a polling interval.

Every 30 minutes, n8n checks the feed. If there's a new item it hasn't seen before, it fires the workflow.

Why RSS instead of a webhook? Most blog platforms (WordPress, Ghost, Webflow, Hashnode, Dev.to) publish RSS feeds automatically. RSS is zero-configuration on the blog side – no webhook setup, no plugin required. If your blog has a feed, you're done.

Stage 2: Input Validation

Before hitting any external API, a Code node validates the RSS item:

const item = $input.item.json;
const title = item.title || '';
const link = item.link || item.url || item.guid || '';

if (!title || !link) {
  throw new Error('Missing title or link from RSS feed');
}

return {
  json: {
    title: title.trim(),
    link: link.trim(),
    description: (item.description || item.summary || '').substring(0, 500)
  }
};

This is simple but important. RSS feeds can have malformed items (especially from older WordPress installs or third-party syndication). Catching bad data early prevents cryptic errors later in the pipeline.

The full version also includes duplicate detection here – it tracks processed URLs in workflow static data and skips items that have already been processed.

Stage 3: Fetching Full Article Content

Here's where most content repurposing tutorials fall short: they use only the RSS excerpt.

RSS descriptions are usually 100-300 words max – often just the post's first paragraph. That's not enough context for OpenAI to generate quality, nuanced social posts that match the full article's tone and key points.

The workflow uses an HTTP Request node to fetch the full blog page HTML, then a Code node extracts the article text:

let content = html;
const articleMatch = html.match(/<article[^>]*>([\s\S]*?)<\/article>/i);
const mainMatch = html.match(/<main[^>]*>([\s\S]*?)<\/main>/i);

if (articleMatch) content = articleMatch[1];
else if (mainMatch) content = mainMatch[1];

content = content
  .replace(/<script[\s\S]*?<\/script>/gi, '')
  .replace(/<style[\s\S]*?<\/style>/gi, '')
  .replace(/<[^>]+>/g, ' ')
  .replace(/&nbsp;/g, ' ')
  .replace(/\s+/g, ' ')
  .trim();

const fullText = content.substring(0, 3000);

It looks for <article> or <main> tags first, strips all HTML, cleans whitespace, and truncates to 3,000 characters – enough content for OpenAI to work with without hitting context limits.

Stage 4: AI Content Generation

The OpenAI node is where the actual work happens. The system prompt is carefully structured to produce consistent, platform-native output.

The prompt enforces per-platform rules: Twitter threads stay under 280 chars per tweet, LinkedIn gets professional paragraph breaks, Instagram gets emoji-friendly storytelling with 20+ hashtags, Facebook gets conversational question hooks, and newsletter snippets create curiosity.

I use GPT-4o-mini by default. It's fast, costs about $0.001-0.003 per post, and produces output that's good enough to publish with minor edits. If you want noticeably higher quality (particularly for LinkedIn), switch to GPT-4o.

The workflow explicitly forces JSON output – no markdown, no code fences. A subsequent Code node parses the JSON and validates all required fields are present.

Stage 5: The AI Fallback Path

This is a feature most tutorials skip, but it matters if you're running this unattended.

If OpenAI is down, rate-limited, or returns invalid JSON, the error output fires instead of breaking the workflow. It routes to a fallback Code node that generates basic posts from the title and excerpt.

The fallback output is basic – but it's better than silence. The Slack message includes a warning that AI generation failed so you know to review it manually.

I've been running this for a few weeks and OpenAI has been unavailable twice during off-hours. The fallback meant zero workflow failures.

Stage 6: Output Delivery

After generation (AI or fallback), three things happen in parallel:

Slack notification: All 5 posts formatted with separators between platforms. Blog title hyperlinked to the original. Hashtags in italic. Delivered to #content.

Google Sheets logging: A content calendar row: date, blog title, URL, all 5 posts, hashtags, AI processed flag, and timestamp.

Buffer integration (optional): Twitter thread and LinkedIn post queued to Buffer for scheduled publishing.

Setting It Up

Prerequisites:

n8n instance (self-hosted or cloud)
OpenAI API key – platform.openai.com/api-keys
Slack workspace + bot app – api.slack.com/apps
Google account (for Sheets OAuth2)
Your blog's RSS feed URL

Setup steps:

Import the workflow JSON into n8n (Workflows → Import from File)
RSS Trigger node: Replace the example feed URL with your blog's RSS URL
OpenAI node: Create a new credential → paste your API key
Slack nodes: Create a new credential → paste your Slack Bot Token
Google Sheets node: Create OAuth2 credential → authorize your Google account
Activate the workflow

Estimated setup time: 5 minutes.

The Results

After running this for a few weeks:

Consistent promotion: Every post gets distributed, not just the ones I have energy for
Better platform fit: GPT-4o-mini actually writes better LinkedIn posts than I do when I'm tired
Time saved: ~2 hours per post → ~5 minutes (review + copy-paste from Slack)
Content calendar filled automatically: The Google Sheets log doubles as a content record

The quality isn't perfect – you'll still want to review and tweak before publishing. But it's a solid first draft that's 80-90% of the way there.

Customization Tips

Change platforms: Edit the OpenAI system prompt to add Reddit, Threads, Pinterest, or YouTube community posts.

Adjust tone: Add a tone directive: "Write in a casual, conversational tone" or "Write for a technical developer audience."

Add a filter: Insert an IF node after the RSS trigger to only process posts with specific categories or tags.

Direct posting: Replace Slack with platform API nodes – though Twitter's API now requires a paid plan ($100/month), so Slack review + manual posting is usually more practical.

Free Template

The free version handles Twitter + LinkedIn (2 platforms) with basic error handling.

Get the free template on GitHub:

https://github.com/flowyantra/blog-to-social-ai-n8n

Download the JSON file from the repo, import into n8n, add your credentials, and you're running.

Full Version

The full version adds:

5 platforms instead of 2 (+ Instagram, Facebook, Newsletter)
Manual trigger for on-demand processing (any URL, not just RSS)
Duplicate detection (never reprocesses the same post)
AI fallback path (always produces output, even when OpenAI fails)
Google Sheets content calendar logging
Buffer integration for scheduled posting
Full retry logic + Slack error alerts

$39 one-time purchase, lifetime updates. If you publish blog content regularly, this saves 2+ hours per post — it pays for itself after your very first blog post.

Get the Full Blog to Social AI Template → $39

More Free n8n Templates

If you found this useful, check out our other free n8n workflow template:

Stripe Payment Notifier – Get instant Slack alerts for every Stripe payment with n8n (free template)

A 4-node n8n workflow that sends real-time Slack notifications whenever a Stripe payment succeeds. No-code webhook automation — 5 minutes to set up.

Browse all templates: flowyantra.gumroad.com

Questions about the setup or customization? Drop a comment – happy to help.

How to Get Instant Stripe Payment Notifications with n8n (Free Template)

FlowYantra — Sat, 21 Mar 2026 02:30:16 +0000

I was checking my Stripe dashboard 10+ times a day just to see if payments came through.

That's roughly 80 hours a year staring at a dashboard. So I automated it with n8n – now I get an instant Slack notification every time someone pays.

Here's exactly how it works, and you can grab the free template at the end.

The Problem

If you process payments through Stripe, you know the drill:

Refresh the Stripe dashboard to check if a payment landed
Check email for Stripe receipts
Ask your team "did that customer actually pay?"

There's no real-time push notification built into Stripe's dashboard. You either poll it manually or set up webhooks yourself.

The Solution: 4-Node n8n Workflow

I built a simple n8n workflow that catches Stripe webhook events and sends formatted Slack notifications in real-time. The entire setup takes about 5 minutes.

Here's the flow:

Stripe Trigger → Validate Event → Format Payment → Slack Notification

Node 1: Stripe Trigger

n8n generates a webhook URL. You configure Stripe to send payment_intent.succeeded events to that URL. Every time someone pays, Stripe pushes the event to your workflow automatically.

No polling. No cron jobs. Instant.

Node 2: Validate Event (Code Node)

Stripe webhooks can occasionally send malformed events, especially during retries. This node checks:

Does the event have a valid type field?
Is data.object present?
Does the payment have an amount field?

If any check fails, the event is rejected before it reaches your Slack channel. This prevents cryptic errors from cluttering your notifications.

const event = $input.item.json;

if (!event.type) {

  throw new Error('Missing event type');

}

if (!event.data || !event.data.object) {

  throw new Error('Missing event data.object');

}

const obj = event.data.object;

if (obj.amount === undefined && obj.amount_received === undefined) {

  throw new Error('Payment event missing amount field');

}

return { json: event };

Node 3: Format Payment (Code Node)

This node extracts the important details from the raw Stripe event and formats them into a clean, readable message:

const event = $input.item.json;

const obj = event.data.object;

const amount = ((obj.amount_received || obj.amount || 0) / 100);

const currency = (obj.currency || 'usd').toUpperCase();

const customerEmail = obj.receipt_email

  || obj.charges?.data?.[0]?.billing_details?.email

  || obj.metadata?.email

  || 'No email on record';

const paymentId = obj.id || 'N/A';

const created = obj.created

  ? new Date(obj.created * 1000).toISOString()

  : new Date().toISOString();

return {

  json: {

    slack_message: '✅ Payment Received\n'

      + 'Amount: ' + amount.toFixed(2) + ' ' + currency + '\n'

      + 'Customer: ' + customerEmail + '\n'

      + 'Payment ID: ' + paymentId + '\n'

      + 'Date: ' + created

  }

};

Node 4: Slack Notification

The formatted message gets posted to your #payments Slack channel. Your whole team sees it instantly – on desktop, mobile, wherever.

No more "hey, did that payment go through?" messages.

What You Need

n8n instance – self-hosted (free) or n8n Cloud
Stripe Secret Key – from Stripe Dashboard API Keys
Slack Bot Token – from Slack API Apps with chat:write permission

Setup Steps

Import the workflow JSON into n8n (Workflows → Import from File)
Add your Stripe Secret Key to the Stripe Trigger node
Add your Slack Bot Token to the Slack node
Create a #payments channel in Slack and invite the bot
Activate the workflow
Test with Stripe test mode (sk_test_...)

Grab the Free Template

The complete workflow JSON is on GitHub – import it directly into your n8n instance:

Stripe Payment Notifier – Free n8n Template

Full Version

The free template covers payment succeeded alerts to Slack. I also built a full version that adds:

Subscription created alerts
Failed charge alerts
Google Sheets logging for all events
Gmail email notifications
Smart event routing with Switch node
Error handling with automatic retries

$39 one-time purchase, lifetime updates. If you process payments through Stripe, this pays for itself in the first week by saving you hours of manual checking and ensuring you never miss a failed charge.

Get the Full Stripe Payment Notifier → $39

Results

After using this for a few months:

Zero missed payments – vs. catching some the next day before
~80 hours/year saved on dashboard checking
Team stays informed without anyone asking
Haven't touched the workflow since setting it up

More Free n8n Templates

If you found this useful, check out our other free n8n workflow template:

Blog to Social AI – Auto-generate Twitter threads & LinkedIn posts from any blog post using n8n + OpenAI

It monitors your blog's RSS feed and uses GPT-4o-mini to automatically create platform-ready social media content. Saves 2+ hours per blog post.

Browse all templates: flowyantra.gumroad.com

If you have questions about the setup or want to customize it for your use case, drop a comment – happy to help.