Mistake: no named owner after go-live
Agencies leave root access in a personal Gmail. When that freelancer ghosts, production is stranded. Name an employee owner on day one with break-glass instructions.
Ownership includes: who may activate workflows, who rotates tokens, who reads error emails. “IT will handle” without a person is not ownership.
Hiring expectations for partners: how to hire an AI automation company.
Fix: RACI in one page
Responsible builder, Accountable business owner, Consulted sales lead, Informed finance for plan costs. Pin it next to the n8n URL.
Mistake: credentials in plain sight
API keys pasted into Function nodes, Slack tokens in workflow notes, shared “admin/admin” on the n8n instance — all common. Credentials belong in n8n credential store with least privilege.
Rotate after every contractor exit. Audit active credentials quarterly.
Self-host instances need SSO or at least strong unique passwords and 2FA where available — see self-host guide linked above.
- Separate staging and production credentials
- Never commit .env files to public repos
- Prefer private app tokens with narrow HubSpot/Zoho scopes
- Log who last rotated WhatsApp BSP keys
Fix: credential inventory sheet
One Sheet (access-limited) listing system, scope, owner, last rotated, expiry. Boring — and it prevents festival outages.
Mistake: open webhooks and surprise traffic
Production webhooks without header secrets or signature checks invite junk data and malicious posts. CRM fills with garbage leads; WhatsApp may fire if filters are weak.
Meta and payment providers often sign payloads — verify signatures in n8n before create operations.
Business-owner explainer: n8n webhooks explained.
Fix: challenge tokens and IP allowlists where possible
Add a shared secret header your form backend sends. Reject missing secrets early with a 401 path that does not touch CRM.
Fix: rate awareness
Queue bursts; do not synchronously create 2,000 Zoho deals because a Sheet import hit the webhook.
Mistake: dual writers fighting the CRM
n8n updates lifecycle stage while HubSpot/Zoho native workflows also update it — and a leftover Zap still runs. Sales sees flickering stages and stops trusting the board.
Pick one writer per critical field. Document it on the field map.
Migration discipline from Zapier reduces dual-writer risk: use the migrate guide linked in the intro.
Fix: automation source property
Stamp `automation_source = n8n-lead-v1` on writes. Filters elsewhere can ignore or detect loops.
Mistake: ignoring error executions
n8n keeps failed executions; nobody looks. Weeks later marketing asks why Meta leads stopped. Error workflows to Slack with workflow name and item id are mandatory.
Distinguish transient HTTP 429 retries from permanent mapping bugs. Infinite retries can hammer APIs and get you blocked.
Weekly 15-minute error triage beats quarterly archaeology.
Fix: dead-letter habit
Park poison messages in a Sheet or queue after N retries for human inspection — do not delete silently.
Mistake: unofficial WhatsApp inside n8n
Community nodes or HTTP calls to WhatsApp Web wrappers appear in forums. They are still unofficial. Ban risk does not care that your canvas looks professional.
Compliant path only: WhatsApp Automation and API vs unofficial.
Log BSP message IDs back to CRM from n8n — skip-logging is its own mistake.
Fix: send-module allowlist
Document the only allowed WhatsApp HTTP base URL (your BSP). Code review any new send node like a payment change.
Mistake: spaghetti workflows without versions
One 80-node workflow named “FinalFinal2” that does leads, invoices, and HR joiners. Untouchable and untestable.
Split by domain. Use naming with ENV prefixes. Export workflow JSON to git if your team can.
If complexity is truly product logic, revisit custom vs n8n — sometimes the mistake is forcing n8n to be an ERP.
Fix: change windows
Do not edit production mapping during peak ad hours. Duplicate workflow, test, then swap activation.
Fix: comment nodes
Sticky notes with why a filter exists save the next hire. Future readers are not telepathic.
Mistake: self-host bravado without ops
A ₹500 VPS with n8n, no backups, Docker forever-outdated, and HTTP not HTTPS. It works until disk fills or a vulnerability lands.
Budget for snapshots, monitoring uptime, and update cadence — or choose hosted Make/Zapier until you can. Details: self-host n8n costs and risks.
n8n Cloud is a valid choice for SMEs who want control of workflows without server duty.
Fix: restore drill
Once a quarter, restore a backup to a staging host and activate a dummy workflow. Backups you never tested are fiction.
Mistake: AI nodes without guardrails
Dropping an LLM node to “personalise everything” sends wrong prices on WhatsApp and invents policy. Keep AI for classification or draft text; keep money and sends deterministic.
PII in prompts is a privacy incident waiting to happen. Minimise fields sent to the model.
Agent vs workflow clarity: AI agents vs workflow automation.
Fix: human approve for high ticket
Draft in n8n, notify owner, send only after approval for deals above your threshold.
Mistake: no measurement, only motion
Fifty active workflows with no KPI is theatre. Tie n8n to minutes-to-first-reply, duplicate rate, or hours saved — measure ROI.
Deactivate unused workflows quarterly. Idle triggers still create risk surface.
Compare tool fit if n8n was the wrong first choice: n8n vs Zapier vs Make.
Fix: monthly automation review
Thirty minutes: top errors, top workflows by volume, cost vs value, and one simplification. Ritual beats heroics.
How Brevia audits and rebuilds n8n from Chennai
We inventory workflows, credentials, webhook exposure, CRM writers, and WhatsApp transport. Then we stabilise one revenue path before cosmetics.
Delivery includes runbook, kill switches, and owner training. Floors from ₹18,000 OTP for scoped n8n work.
Start: consultation or contact. Service: n8n Automation in India.
What “done” means
Authenticated webhooks, one writer per critical field, error alerts staff actually read, official WhatsApp only, and a restore path if self-hosted. Everything else is backlog.
Ready to automate one painful workflow?
Tell us your stack — n8n, Make, Zapier, WhatsApp, or Playwright. Chennai HQ · India delivery · reply within one business day.