Routing contact-form leads into a CRM with n8n: dedupe, enrich and alert without losing a request

WeRumo — Sun, 01 Nov 2026 20:13:16 +0000

Small service businesses lose leads in boring ways: a form email lands in a shared inbox, two people answer it, or nobody does. Here is the n8n flow we use for client projects to make every request land in the CRM exactly once and reach the right person within a minute.

The flow

Webhook trigger. The site form posts JSON to an n8n Webhook node. Respond immediately with 200 so the visitor never waits on downstream steps.
Normalize. A Set node trims whitespace, lowercases the email and maps the form's service field to a fixed list of values.
Dedupe. Search the CRM for a contact with that email. If found, add a note to the existing deal instead of creating a new one.
Create or update. An IF node branches into "create contact + deal" or "append note".
Route. A Switch node on service picks the owner and posts to that person's Slack or Telegram channel with a link to the CRM record.
Error workflow. A separate Error Trigger workflow catches any failed execution and sends the raw payload to an ops channel, so a broken API key never silently drops a lead.

Details that matter

Store the raw payload in a data table before any API call. If the CRM is down, you can replay it.
Use an idempotency key (a hash of email + timestamp rounded to a minute) to stop double submissions.
Keep credentials in n8n's credential store, never in Set nodes.
Log timings per node for the first week; the slow step is rarely the one you expect.

n8n vs Make vs Zapier

Self-hosted n8n wins when data must stay on your own server, for example GDPR-sensitive intake in the EU. Make is faster to hand over to a non-technical owner. Zapier is the simplest for two-step flows but gets expensive with volume.

Disclosure: I work at WeRumo, where we build flows like this for small businesses in Germany — process automation services.

How We Built a Zero-Database, High-Performance Multilingual Platform for German Relocation & Business Setup

WeRumo — Sat, 31 Oct 2026 17:39:10 +0000

When architecting software solutions for the German corporate and relocation ecosystem, technical architecture quickly collides with stringent legal frameworks. Between GDPR (DSGVO), statutory retention requirements, and cross-border identity processing for expatriates and corporate founders, persisting personal records in persistent SQL databases introduces significant operational and compliance liability.

At WeRumo, we took a fundamentally different engineering route: building a zero-database, static-first, edge-orchestrated architecture designed specifically for high-speed delivery, strict compliance, and effortless multi-language internationalization.

In this deep dive, we break down how we designed the platform, eliminated database attack vectors, and optimized our infrastructure for 100/100 Core Web Vitals across Europe.

1. The Architectural Challenge: Compliance by Design

Building digital tools for German business formation (UG & GmbH setup) and skilled immigration dossiers (§ 18g AufenthG EU Blue Card, § 20a Chancenkarte) involves handling sensitive corporate and personal metadata:

Notarial articles of association (Musterprotokoll / Satzung)
Residential confirmations (Wohnungsgeberbestätigung pursuant to § 19 BMG)
Commercial register excerpts (Handelsregisterauszug)
Proof of Stammkapital deposit and Sperrkonto confirmations

Under GDPR Art. 5 (Data Minimization) and Art. 17 (Right to Erasure), storing intermediate documents and applicant PII in a centralized SQL cluster creates extensive overhead: audit logs, encryption at rest, token rotation, automated purge scripts, and leak surfaces.

The Solution: Decouple public interaction, questionnaire pipelines, and document drafting from persistent web databases.

2. Frontend Architecture: Edge-Rendered, Multi-Regional Next.js

Our web layer is built on Next.js with TypeScript and Tailwind CSS, deployed to distributed edge networks.

A. Static Dictionaries with Zero Runtime Penalty

Rather than querying dynamic localization tables, our multi-locale architecture (/en, /de, /ru, /uk) utilizes pre-compiled immutable locale trees.

export const supportedLocales = ['en', 'de', 'ru', 'uk'] as const;
export type Locale = (typeof supportedLocales)[number];

By compiling all routes at build time with Incremental Static Regeneration (ISR), Time to First Byte (TTFB) is kept under 35ms across European edge nodes without any cold-start database connection pool latency.

B. Component Hierarchy & Accessibility

Every interactive module adheres strictly to WCAG 2.1 AA accessibility guidelines, semantic HTML5 landmarks, and structured JSON-LD Schema markup (Organization, Service, FAQPage), providing rich indexing for search engines and AI web crawlers.

3. Stateless Form Pipelines & Transient Edge Processing

How does a platform process business inquiries and service requests without a database?

[ Client Browser ]
        │  (Client-side Zod validation)
        ▼
[ Edge API Middleware (Next.js Route Handler) ]
        │  (HMAC Signature + Rate Limiting + Schema Sanitization)
        ▼
[ Transient Encrypted Webhook (n8n Orchestration) ]
        │
   ┌────┴────────────────────────┬─────────────────────────┐
   ▼                             ▼                         ▼
[ Direct Alert Bot ]      [ PGP Encrypted Mail ]    [ Ephemeral Buffer ]

Client-side Verification: Every input (tax IDs, company registration numbers, visa timelines) is validated client-side via type-safe zod schemas.
Edge Route Handler: When submitted, an ephemeral Edge Route Handler verifies an HMAC token, strips untrusted properties, and validates origin headers.
Event Dispatch: Instead of executing an INSERT INTO users query, the payload is converted into an encrypted event dispatched directly to a self-hosted, hardened n8n workflow runner.
Transient Storage: Data is processed instantaneously into actionable operational alerts and encrypted customer receipts, leaving zero residual footprint on web-accessible servers.

4. Zero-DB Security Benefits in Numbers

By eliminating traditional web databases:

Zero SQL Injection Vector: There is literally no database engine running behind the public API routes.
Zero Inactive PII Exposure: A data breach of the web server yields zero persisted customer databases, password hashes, or identity records.
DDoS Resilience: 99.8% of platform assets are cached statically at CDN edge nodes, reducing server CPU compute spikes during traffic surges.
Near-Zero Infrastructure Footprint: Serverless execution and static assets mean hosting costs remain flat even as consultation volume scales.

5. Key Takeaways for Full-Stack Teams

When building platforms in regulated industries:

Challenge the 'Default Database' assumption: Not every interactive web application needs a persistent PostgreSQL or MongoDB backend.
Lean on Edge & Workflow Engines: Moving state management and document routing to specialized workflow orchestrators (like n8n) drastically simplifies web architecture.
Make Performance Part of SEO: Instant static page loads directly boost conversion rates and domain authority.

To inspect how this architecture operates live in production for international founders and expatriates, visit the live deployment at WeRumo Consulting.

What are your thoughts on zero-database architectures for compliant business platforms? Let's discuss in the comments below!

DEV Community: WeRumo