n8n for Orchestration and Integrations
n8n is a workflow automation tool that connects systems through nodes: triggers, transformations, and actions on external or internal services.
At Coresis we use it for the integration layer: moving information between CRM, ERP, databases, email, messaging, and our own APIs. It's often the part that determines the real timeline of an automation project, more than the language model.
Main capabilities
Integration before intelligence
Most processes are solved by connecting systems correctly. The language model is reserved for where it adds value, not for everything.
Rules where rules are enough
A deterministic flow is cheaper to operate and easier to audit than a decision delegated to a model. n8n makes it possible to keep that separation explicit.
Self-hostable
It can be deployed on your own infrastructure, so sensitive data never has to leave the perimeter. This is a common requirement in banking, healthcare, and the public sector.
Execution traceability
Every execution is logged with its input, its output, and its error if there was one, which makes an automated process diagnosable.
A license worth reviewing
n8n uses the Sustainable Use License: it allows internal use but not offering it as a commercial service to third parties, and its enterprise features require a separate license. It isn't OSI-approved open source.
When we choose n8n
n8n fits when the process crosses several systems and the difficulty lies in integration and error handling. When it also needs natural-language conversation with scoped tools, we combine it with Dify. You can see the full picture at our AI agency.
Frequently asked questions
Is n8n open source?
No. It uses the Sustainable Use License, which allows internal or non-commercial use but not offering the software as a service to third parties. It's source-available, not OSI-approved open source.
Does it replace custom development?
Sometimes yes, sometimes no. For moving data between systems with clear rules, it's usually faster and more maintainable. When the business logic is dense, custom development turns out to be more sustainable.
Can it integrate with Drupal?
Yes, through Drupal's API or webhooks. It's commonly used to sync content, notify publications, or connect forms with internal systems.
Decision guide
When to automate a process with n8n
n8n is useful for coordinating APIs, data, and actions with a visible flow. It lets you ship automations quickly, but a reliable process also needs idempotency, retries, credential control, and owners. The priority should be a deterministic rule; AI is only added where it adds value.
System synchronization
Moving and transforming information between CRM, ERP, email, forms, and our own APIs.
Approval processes
Preparing information, requesting a human decision, and continuing only when there's evidence.
Event orchestration
Receiving webhooks, validating data, and triggering actions with traceability for every execution.
How it fits into the architecture
A trigger starts the flow; nodes validate, transform, and call services; and durable state stays in the system of record, not hidden inside an execution. For volume, workers and queues are separated. Credentials are isolated, webhooks are authenticated, and every operation that could repeat is designed not to duplicate effects.
What to validate before adopting it
- Define the owner, input, output, and success state of the process.
- Apply idempotency, limits, retries, and a recovery path.
- Restrict credentials and data visible in the execution history.
- Version, test, and deploy flows like any other software.
When not to choose it
n8n shouldn't turn into a full enterprise application inside a diagram. Complex transactional rules, high concurrency, or a product experience may need Node.js and NestJS. It's also not a good idea to use an agent for a decision that can be expressed with verifiable conditions.
How Coresis applies it
Coresis uses n8n for scoped integrations and automations. When the flow incorporates language it can call agents built with Dify; when it needs a maintainable API it relies on Node.js or NestJS.
Source and related technologies
Compare capabilities and limits in the official n8n documentation.