n8n automation
Production n8n workflows, built around your systems and your team.
n8n implementation for repeatable workflows across CRM, operations and reporting. Make the rules visible, handle exceptions and keep people in control of consequential actions.
Illustration: an n8n workflow canvas with five numbered nodes, Trigger, Validate, Check existing record, Approval needed? and Write record, plus an approval branch and a dashed Failure queue branch.
Check whether n8n fits the workflow.
n8n can join systems and make a repeatable sequence visible, but drawing a line between nodes is not the same as deciding who owns a customer record. We start with one process, its source of truth and the decisions a person still needs to make. A tool-based workflow is useful when integrations are defined and operators can inspect the result. A complex transaction may belong in application code instead.
A guide for the first conversation, not an assessment.
Is the rule settled: who owns each record, consent and approval?
- Yes
- Question 2
- No
- Settle the policy first
Does the work cross more than one system?
- Yes
- Question 3
- No
- Keep the rule in the source system
Is it a complex transaction, where several changes must succeed or fail together?
- Yes
- Consider application code
- No
- Question 4
Are the integrations defined, and can operators inspect the result?
- Yes
- A workflow fits
- No
- Keep the rule in the source system
Where the first conversation starts
- Question :
- Question :
- Question :
- Question :
Answer the questions in order. Each route ends at one of these starting points:
- A workflow fits
- Settle the policy first
- Consider application code
- Keep the rule in the source system
A workflow fits
A tool-based workflow is useful when integrations are defined and operators can inspect the result.
Settle the policy first
If lead ownership, consent, invoice approval or escalation timing is undecided, n8n will only execute an ambiguous rule faster. We ask the business to settle those points before connecting a live channel.
Consider application code
A complex transaction may belong in application code instead.
Keep the rule in the source system
We compare the visibility and change needs of a workflow with the capabilities of your existing applications and direct integrations. A smaller rule in the source system may be more reliable than another moving part.
Build the path and the exception together.
The implementation follows the business process rather than a prebuilt diagram. Each step may read, enrich, approve or write only what its task needs, and every exception has a place to go.
Event and data contract
Define what starts the flow, which fields are required and which system may create or correct each record. Decide how repeated events are recognized.
Controlled actions
Separate reading, enrichment, approval and writing. Limit provider permissions and require human review where an automated decision could affect a customer or payment.
View CRM & API integrationsOperational view
Record successes, exceptions and attempts so staff can investigate a failed step without exposing secrets or unnecessary customer data in logs.
View Automation maintenanceCheck existing record
A read before any write, so a repeated event is recognized instead of creating a second record.
Approval needed?
A person approves before an action that could affect a customer or payment, and the workflow waits for that decision.
Write record
The narrowest write the task needs, made only where that system may create or correct the record.
Choose how n8n will run.
n8n distinguishes its managed Cloud option from self-hosting, and the deployment choice is separate from the plan or edition. Confirm the current features and limits the project needs before choosing.
| Question | n8n Cloud | Self-hosted n8n |
|---|---|---|
| Who runs the environment | n8n, as a managed service | Your operator, including infrastructure, upgrades, recovery and administration |
| When it fits | The team wants a managed service and the chosen plan includes the controls it needs | Deployment control matters and someone can maintain the installation |
| What to confirm | The current features and limits of the plan | The edition, and the license terms for the intended use |
| What continues after delivery | The subscription and external provider usage | Hosting, backups, upgrades, incident handling and external provider usage |
Self-hosted n8n is not automatically cheaper. An internal workflow and a service that gives paying customers access to an automation platform are not automatically the same licensing situation.
Test with real states, safe data and the people who act.
The owner reviews a successful request, an incomplete one, a duplicate and a destination outage. We test how an operator learns that work is waiting and what can be retried. Changes are introduced through a controlled environment and a recorded version, with provider credentials held in approved storage. The first production route should be narrow enough that the team can observe and correct it.
Expected outcome
A successful request
The record is written once and the responsible person is told.
An incomplete request
Nothing is written; the request waits visibly for the missing information.
A duplicate
The repeated event is recognized, and no second record or message is created.
A destination outage
The accepted work is retained, the attempt is recorded and an operator can see what is waiting.
The workflow cannot invent a missing policy.
If lead ownership, consent, invoice approval or escalation timing is undecided, n8n will only execute an ambiguous rule faster. We ask the business to settle those points before connecting a live channel. Provider subscriptions, hosting, data retention and message costs belong in the scope. Sensitive data handling and cross-border transfer need review against the actual systems used; a node library does not settle them.
Make the diagram maintainable after delivery.
The handover gives your team what it needs to run, pause and change the workflow. Ongoing hosting or maintenance is agreed separately, with a clear owner for future changes.
Trigger and field mappings
What starts the workflow and how each field maps between systems.
Account ownership
Who holds each provider account and credential.
Failure queue
Where failed work waits and who reviews it.
Pause and rollback steps
How to stop the workflow safely and return to the previous version.
Messages and approvals
Which messages the automation is allowed to send and which actions require approval.
Known limits
The limits of the workflow and any manual reconciliation that remains.
Before you commit to n8n.
Compare the tools on your own workflow, see what drives the estimate and follow one enquiry through a connected workflow.
n8n vs Make vs Zapier for your workflow
Compare the tools on the specific workflow, its required connectors, governance and operating responsibility.
Read the guide: n8n vs Make vs Zapier for your workflowWhat does n8n implementation cost?
The rules, integrations, reliability needs and operating model that drive the estimate.
Read the guide: What does n8n implementation cost?Lead workflow walkthrough
Follow an enquiry through validation, routing and recovery, and the decisions that keep the workflow accountable.
See the walkthrough: Lead workflow walkthrough
Some of the teams we have worked with.
Across talent, fitness, mobility, payments and local commerce.Questions about n8n projects.
Must every process use n8n?
No. We compare the visibility and change needs of a workflow with the capabilities of your existing applications and direct integrations. A smaller rule in the source system may be more reliable than another moving part.
What happens when a connected service is unavailable?
The design should retain the accepted work, record an attempt and show a human what is waiting. Safe retry depends on the action and whether the destination may already have applied it.
Should we use n8n Cloud or self-host it?
It depends on who will run the environment. n8n Cloud is the managed option; self-hosting gives your operator responsibility for infrastructure, upgrades, recovery and administration. Self-hosted n8n is not automatically cheaper, and the license terms should be checked for the intended use.
Continue exploring
Continue exploring
Lead capture & follow-up
We connect your website forms, inboxes and campaigns to your CRM, so each enquiry is accepted once, reaches the right person with its context and stays visible until someone has followed it up.
View Lead capture & follow-upAI & automation
Business automation, CRM integrations and AI implementation for defined operational tasks. Connect systems without hiding the rules or the exceptions.
View AI & automationTechnology expertise
Platform expertise across content, commerce, applications and mobile. Compare the fit, operating cost and maintenance implications before committing to a stack.
View Technology expertise
Bring one workflow, including the run that fails.
Describe the trigger, the systems it touches and what should happen when a step fails. We can tell you whether n8n fits and scope a first production route your team can observe.
Technology names and marks belong to their owners.