# n8n and Make automation

> n8n and Make automation means building, hosting and maintaining the data flows between your systems on these two workflow tools. Corrplus sets up n8n on your own server or on n8n Cloud, and Make in the cloud, and connects them to the systems you run, including Turkish ERPs, marketplaces, e-invoicing providers and the WhatsApp Business Platform.

URL: https://corrplus.net/services/workflow-automation/n8n-make-automation/
Updated: 2026-10-22
Corrplus Team

## Who it is for

- Companies that have chosen n8n or Make and want an experienced team for setup and the first workflows
- Teams that inherited n8n or Make workflows someone built and left, and need them put in order
- Organisations that want n8n self-hosted so data stays on their own infrastructure
- Teams moving off Zapier because of cost or limits

## When it is not a fit

- Companies that have not decided which process to automate yet. We start with general workflow automation instead.
- Systems with no API that can only be used through a screen. Those need RPA.

## What you get

- **A running n8n or Make environment**: Self-hosted n8n on Docker and PostgreSQL, an n8n Cloud account or a Make organisation, with all access in your name.
- **Working workflows**: Workflows tested on your real data, each doing one job, with a clear name and written purpose.
- **Reusable integration blocks**: Shared sub-workflows for services that have no ready-made node, such as Turkish ERPs, marketplaces and e-invoicing providers.
- **Error handling**: A central error workflow, retry rules and alerts by email, Teams or WhatsApp when something fails.
- **Versioning and backup**: Workflows exported and stored as JSON, and backups of your self-hosted instance.
- **Documentation**: Notes your team can follow to read the workflows and make small changes themselves.

## How we work

- **Discover**: In a free first call we review the systems to connect and any workflows you already have.
- **Design**: We decide together on hosting, workflow structure and where personal data is processed, and write it down.
- **Build**: We set up the environment and deliver workflows in short cycles, each ending with a version running on real data.
- **Run**: We track version updates, backups and alerts, and update workflows when APIs change.

## Tools we use

n8n (self-hosted and n8n Cloud), Make, Docker, PostgreSQL, Redis, Marketplace and ERP APIs, WhatsApp Business Platform, Microsoft 365 and Google Workspace, OpenAI and Anthropic Claude models

**Timing:** Setup and the first workflow usually within 2–4 weeks

**Pricing:** Fixed-scope project quoted after the discovery call; optional monthly maintenance and hosting support. n8n Cloud or Make subscriptions are not included.

## How is this different from workflow automation?

Our [workflow automation](/services/workflow-automation/) page covers the broader service, where we decide which work to automate and which tool to use. This page is narrower. This page is for you if you have already settled on n8n or Make, or you have workflows someone built and left behind. The focus is setting up these two tools, hosting them, connecting them to your systems and keeping them running for the long term.

## Self-hosted n8n, n8n Cloud or Make?

| Aspect | n8n (self-hosted) | n8n Cloud | Make |
|---|---|---|---|
| Where data is processed | Your own server, in the region you choose | n8n's cloud | Make's cloud |
| Server maintenance | You or us | n8n | Make |
| Custom code | JavaScript and Python code nodes | Same | Possible, but more limited |
| Best for | Teams with technical staff or a maintenance partner | Technical teams that do not want to run servers | Companies where business users edit workflows too |
| Data protection | Can run without data leaving your infrastructure | Needs a transfer assessment | Needs a transfer assessment |

We run self-hosted n8n on Docker and PostgreSQL. When volume grows, we switch on queue mode with Redis to spread executions across several workers.

## Which integrations do you build?

Many services have no ready-made node in n8n or Make. We connect them over HTTP and turn them into reusable sub-workflows. For companies operating in Türkiye, typical connections are orders and stock from the Trendyol and Hepsiburada seller APIs, invoices in Paraşüt, your e-invoicing provider's API, database or web service links to local ERPs such as Logo, Mikro and Netsis, iyzico payment notifications, SMS through Netgsm and the WhatsApp Business Platform. Internationally, the same approach applies to your CRM, ERP and internal tools.

## We take over existing workflows

A common situation: someone built the workflows a few years ago and then left. No workflow has a meaningful name and nobody notices when one fails. When we take over, we list every workflow, switch off the unused ones and add a central error workflow with alerts to the rest. Workflows are exported as JSON and stored regularly, so a breaking change can be rolled back.

If one of your systems has no API and can only be used through a screen, n8n or Make will not be enough; see [RPA consulting](/services/workflow-automation/rpa-consulting/) for that step. In the first call we review the systems to connect and the workflows you already have.

## Frequently asked questions

### Should we use n8n or Make?

Choose n8n if data must stay on your own servers, you want to write code, or volumes are high. Make is easier if you have no technical team and business users will edit workflows too. We decide together based on your systems and data protection needs.

### Is self-hosted n8n free?

The self-hosted Community edition of n8n has no licence fee. Server, updates, backups and monitoring are still your cost. We can take that work on as part of monthly maintenance.

### Can self-hosted n8n help with GDPR?

It gives you control over where data is processed, because workflows run on your own infrastructure, in the EU, in Türkiye or wherever you need. Whether that meets your obligations is a question for your legal counsel; we make the technical setup match their answer.

### How does a move from Zapier work?

We list your existing Zaps, rebuild each one in n8n or Make, and run both sides in parallel for a while to compare results. The move is complete when the results match.

### Whose account do the workflows run in?

Yours. n8n runs on your server or in your n8n Cloud account, Make in your organisation. All access and documentation is handed over to you.

### Can we add AI to the workflows?

Yes. n8n and Make can call OpenAI, Anthropic Claude and Google Gemini models. Steps such as classifying an email, extracting fields from a PDF or drafting a reply are added to the workflow, with human approval where it matters.