n8n · Automation

5 n8n Workflows Every German SME Should Have Running This Week

These aren't demos. They're production workflows running right now in our own system and in client deployments across Germany. Copy the architecture. Adapt the credentials. Ship this week.

June 3, 2026 · 7 min read · Bratschke Solutions GmbH

Most n8n tutorials show you how to send a Slack message when a form is submitted. That's not automation — that's a webhook with extra steps.

Real automation eliminates decision-making. It takes data from one system, applies logic, and updates another system without a human in the loop. Here are five workflows that do exactly that — all deployed in the real world, all DSGVO-compliant, all achievable in under a day.

23havg. saved per week
5workflows below
0recurring human tasks
€0extra software cost
Workflow 01
Lead Capture → CRM Enrichment → Slack Alert

A new lead fills out your Typeform or HubSpot form. Within 30 seconds: the contact is created in your CRM, enriched with company data from Clearbit (or a German alternative like Echobot), scored by industry/company size, and the responsible sales rep gets a Slack DM with a one-sentence summary.

Why this matters: The average German SME responds to inbound leads within 47 hours. With this workflow, the rep has context before the lead even opens their laptop.

Typeform / HubSpot Form HTTP Request (Clearbit) IF (score logic) HubSpot / Pipedrive Slack
⏱ Saves ~4h/week in manual lead logging
Workflow 02
Overdue Invoice → Reminder Sequence → Escalation

Every morning at 07:00, this workflow scans your accounting system (DATEV, Lexware, Sevdesk — all have APIs or export formats) for invoices past their payment term. It sends a friendly first reminder via email, waits 5 business days, sends a firmer second reminder, then after another 7 days escalates to your accounting team with a structured alert including days overdue, invoice number, and client contact.

DSGVO note: All processing happens on-premise or in your n8n self-hosted instance. No invoice data leaves your infrastructure.

Schedule Trigger (daily) HTTP Request (accounting API) Filter (overdue logic) Wait node (5 days) Gmail / SMTP Slack (escalation)
⏱ Saves ~6h/week in manual follow-up calls and emails
Workflow 03
Weekly KPI Report → PDF → Email → Telegram

Every Monday at 06:30, this workflow pulls the previous week's numbers from your data sources (Google Analytics, Stripe, HubSpot, or a Postgres database), formats them into a structured HTML template, renders it to PDF via a headless browser, and delivers it to your management team via email and Telegram.

No more "can someone pull the numbers before the Monday meeting." The numbers are in everyone's inbox before they arrive.

Schedule Trigger (Mon 06:30) Postgres / HTTP APIs Code node (formatting) HTML Template Gmail Telegram
⏱ Saves ~3h/week in manual reporting
Workflow 04
New Customer → Onboarding Sequence (7-Day)

When a new customer is created in your CRM or when a Stripe subscription starts, this workflow kicks off a 7-day onboarding sequence: Day 0 welcome email with credentials, Day 1 product tour nudge, Day 3 first-use check (via API call to see if they've logged in), Day 7 success check-in. If Day 3 shows no activity — an automatic flag goes to your customer success team.

This workflow alone typically lifts 30-day retention by 12–18% in the deployments we've measured.

Stripe Webhook / CRM trigger Wait node (1 day) Gmail sequence HTTP Request (product API) IF (activity check) Slack (CS alert)
⏱ Saves ~5h/week + improves retention
Workflow 05
Support Inbox → Triage → Priority Routing

Incoming support emails hit a shared inbox. This workflow classifies them by topic (billing, technical, onboarding, complaint) using a keyword-matching code node or a Claude API call for semantic classification. High-priority tickets (billing issues, complaints) go directly to a Slack channel with @channel. Technical issues are forwarded to your dev team's queue. Onboarding questions get an immediate templated response.

Result: your support team handles only the tickets that actually need a human — typically 30–40% of volume.

Gmail / IMAP trigger Code node (classification) Switch node Gmail (auto-reply) Slack (routing) Jira / Linear (ticket)
⏱ Saves ~5h/week in inbox triage

The Setup Reality

These workflows take between 2 and 8 hours each to configure, test, and deploy — assuming you already have n8n running. If you're starting from scratch with a self-hosted n8n instance, add a day for infrastructure setup.

The harder part isn't the n8n configuration. It's the integrations: API keys, webhook URLs, credential permissions, DSGVO-compliant data routing decisions. That's where most DIY automation projects slow down or stop.

Common bottleneck: DATEV doesn't have a direct REST API — you need a middleware (DATEV Unternehmen online, or a third-party connector). Same with some German banking systems. These integrations exist, but they require configuration that takes longer than the n8n part.

What We Actually Do for Clients

We configure and deploy these workflows as part of our AI agent system. The difference: instead of five isolated automations, everything connects to a central intelligence layer. The lead workflow feeds data to the KPI workflow. The support triage feeds patterns back to the onboarding sequence.

That's the gap between automation and an agent system. Automations react to events. Agent systems learn from patterns and adjust.

For most German SMEs currently spending €3,000+/month on manual processes, the automation layer alone — these five workflows — justifies the entire engagement cost in the first 60 days.

Want These Running in Your Business?

We configure, deploy, and maintain n8n workflows for German SMEs. DSGVO-compliant, self-hosted, integrated with your existing tools. Free 30-minute scoping call — we map which workflows fit your stack first.

Book a Free Scoping Call

BAFA-eligible · Setup in 1–2 weeks · €499/month founding rate