n8n + Claude Workflow Architecture

The problem

Businesses need workflow automation that scales without vendor lock-in — but pre-built platforms (Make, Zapier) create dependencies. Teams need to see and modify flow logic without touching code, but low-code platforms hide logic or require custom code anyway. AI reasoning should be integrated into workflows but not control them.

Approach

Layer 1 — Triggers: Webhooks (Shopify, Meta, Stripe), cron schedules (daily / hourly), user actions (form, quiz, click), external APIs (email, WhatsApp).
Layer 2 — Orchestration: n8n handles intake + validation, the bucket resolver routes by intent + catalog lookup, Claude is called as a structured-JSON tool for reasoning steps, IF nodes + error handlers do branching / retry / formatting.
Layer 3 — Delivery: WhatsApp (templates + sessions), email (SMTP / Resend / SES), CRM sync (Privyr / HubSpot / Notion), database (Supabase / Postgres), Google Sheets (reporting).
n8n owns all flow logic — branching, retries, error handling, observability — in one place where clients can see and modify without code.
Claude called only as a structured-output JSON tool for specific reasoning (intent classification, content generation) — cheap to run, easy to debug.
Self-hosted by default on a $5/month VPS in Docker — survives platform pricing changes, full data control.
The Bucket Resolver pattern is reusable across clients: given user intent + catalog, route to appropriate branch. Same module adapts to different client catalogs.

Results

5+ production deployments across e-commerce, agency ops, and SaaS use cases.
Real shipped use cases: cart abandonment recovery, browse recovery, customer-service AI routing, quiz-to-recommendation, reviews migration (e-commerce); multi-client report generation, ad-campaign monitoring + alerts, automated client onboarding (agency ops); user-onboarding sequences, activity-based notifications, AI content scheduling (SaaS).
Zero vendor lock-in through self-hosting and portable component design.
~$5/month hosting cost vs. platform fees that scale with volume.
Reusable playbook — same architecture deployed with different integrations per client.

n8n owns the flow logic — clients see and modify it without code. Claude is a tool, not the boss — called for specific reasoning steps only. Self-hosted by default, no vendor lock-in. Bucket Resolver pattern reusable across clients with different catalogs. This pattern works for e-commerce, agency ops, and SaaS — the architecture I deploy everywhere.

Tech stack

n8n (self-hosted)Claude APIDockerWebhooks (Shopify / Meta / Stripe)WhatsApp BusinessSupabase / PostgresGoogle SheetsPrivyr / HubSpot / Notion

Need this kind of work done?

Open to consulting and contract work in AI automation, ad operations, and GEO. Same approach, same metrics-driven rigor.

Work with me See other case studies