Automating processes with n8n without breaking what already works

n8n is a workflow automation tool: it connects applications (WhatsApp, email, spreadsheets, CRM, invoicing) with nodes you drag on a canvas and, when needed, with code. It is open source and can be hosted in your own cloud, which matters when data cannot leave the company.

What n8n is and when to choose it over Make or Zapier

For a company with hundreds of operations a day or with sensitive data, self-hosted n8n usually comes out ahead. For three small marketing automations, Make or Zapier are fine.

How to choose the first process

• It happens every day and someone does it by hand, copying data between two systems.
• It has a clear input and output: a form arrives, a CRM record and a WhatsApp message go out.
• If it fails, it shows fast and can be redone by hand without damage.
• It does not touch money the first time. Payments and invoices come later, with human approval.

A pattern that holds: receive, validate, act, log, notify

1. Receive: a webhook or a scheduled trigger.
2. Validate: required fields, phone format, duplicates. If something fails, the flow ends here with a notice.
3. Act: create, update or send. One action per branch.
4. Log: one row per run with date, input, result and error if any.
5. Notify: a short message to the responsible person only when something needs their attention.

What to check before leaving it alone

• Dedicated credentials for n8n in each system, with least privilege. Never someone's personal account.
• Retries with a limit on API calls and an error queue someone reviews every day.
• Backups of the flows (they export as JSON and go into Git).
• A test with 20 anonymized real records before opening it to live traffic.
• A named owner for every flow: who fixes it when the provider's API changes.

Automating a broken process only breaks it faster. Process first, flow second.