PAS7 Studio
Paper nodes join and branch into two different shapes
Studio18 Nov 2026··6 min read·Updated 18 Nov 2026

n8n, Make or Custom Code: Choosing in 2026

Compare n8n, Make and custom code by pricing, reliability and support, with a 12-month cost example and migration plan.

You may not need custom code

If a process receives a lead, records it in a CRM and notifies the team, first check the integrations available in Make or n8n. A custom service makes sense when platform limits, control requirements or long-term costs justify building and maintaining it.

Choose the process, not the logo: how many events arrive each month, how quickly must they be handled, who fixes failures and what happens if one event is processed twice? A visual workflow changes implementation, not the need to answer these questions.

Three approaches and their trade-offs

CriterionMaken8nCustom code
Getting startedHosted visual service with ready-made modules.Visual workflows in the cloud or on your own infrastructure depending on the edition.Requires development, deployment and service maintenance.
VolumeBudget credits for module actions; branching and retries affect use.Paid plans are based on workflow executions; check the limits of the particular plan.Budget for load, hosting, queues and engineering time.
Data controlReview the hosted service’s terms and integration access.Self-hosting offers more control over the environment but adds operational duties.You can choose architecture and placement, while the team owns the responsibility.
SupportA workflow owner must watch limits, credentials and errors.A workflow owner is needed; self-hosting also needs infrastructure administration.An engineer or team needs access to the code and operational responsibility.
SLACheck the chosen plan and dependent services.Check the edition, support terms and your own response capacity.Service level depends on architecture, staffing and the agreed support.

Three scenarios and a verdict

Lead → CRM → notification. If the connectors exist, volume is modest and the team wants to edit messages without a developer, start by evaluating Make. n8n can also fit; compare its integrations, price and access ownership. Define duplicate handling and CRM outage behavior before launch.

An internal process across several systems. If you need your own hosting and have technical staff, consider self-hosted n8n. Control comes with updates, backups, secret protection and monitoring. Check the license for your access model, especially if clients edit workflows. [2]

A large flow with unusual logic. Consider custom code when you need complex processing, precise queue control, integrations without suitable modules or specific testing requirements. Volume alone does not prove savings: estimate development and support alongside the platform alternative.

One lead is not necessarily one credit

Illustrative scenario: a CRM sends 1,000 events per month, each triggering a workflow that receives the event, adds a spreadsheet row and sends a notification. If each of those three Make steps consumes one credit, the baseline estimate is 1,000 × 3 = 3,000 credits. This is an assumption, not a measured scenario. Actual modules, batching, retries, empty polling and extra actions change the result. [1]

Under the same assumptions n8n would run approximately 1,000 workflow executions if each event starts one execution. Extra or test runs change the number; Make credits and n8n executions are not equivalent units. The n8n Starter page lists 2,500 monthly executions at €20 per month billed annually, checked 11 November 2026. This is a plan snapshot, not the complete automation budget. [3]

Map the actual steps, test a sample on the chosen plan, inspect the usage meter and allow for peaks, retries and growth. AI modules can have different pricing and external APIs can charge separately. [1]

When does custom code pay off? A 12-month example

All figures below are fictional assumptions to illustrate the calculation. They are not Make, n8n or PAS7 prices or a project quote. Both options assume the same scope and support; taxes, scope changes and third-party API charges are excluded.

CostPlatformCustom code
Initial setup€300€900
Monthly cost including support€70€20
12-month total€300 + 12 × €70 = €1,140€900 + 12 × €20 = €1,140

The hidden cost is not just the subscription

Identify who receives error alerts and can replay an event without creating a duplicate CRM record. Keep a stable event ID, define processing state and set a retry limit. If the spreadsheet fails after the CRM write succeeds, replaying the entire workflow without checking can duplicate the record.

Make’s incomplete-execution storage must be enabled; automatic retries depend on error type and configuration. Test a failure instead of assuming every event recovers automatically. [4] For n8n and custom code, also define failure storage, alerting, backups and recovery responsibilities.

How to migrate without losing events

  1. Document the source, fields, event ID, actions, owner and expected result. Export configuration and document access without copying secrets into documents.
  1. Build the replacement with test data. Exercise the normal path, duplicate event, timeout and outage of each integration. Agree who recovers failures and how.
  1. Compare the new and old paths on the same events in a test mode without duplicate real writes or notifications. Reconcile outcomes and define the cutover and rollback.
  1. After cutover, monitor the queue, failures, duplicates and cost. Turn the old process off only after reconciliation and the agreed observation period.

Sources

Need an automation estimate?

Describe your data source, desired outcome and event volume. PAS7 can help define the scope and compare implementation options.

Related Articles

Business Process Automation Cost in 2026: CRM, API, Webhooks, Leads and Workflow
business-automation

Business Process Automation Cost in 2026: CRM, API, Webhooks, Leads and Workflow

A practical buyer guide to business process automation cost: CRM integrations, website leads, API and webhook flows, notifications, documents, reporting, and support.

Integrations: GDrive, S3, Notion for Content Organization
telegram-media-saver

Integrations: GDrive, S3, Notion for Content Organization

Using official APIs to integrate with GDrive, AWS S3, Notion, and other services

Telegram Bot Webhook vs Polling: Deploy grammY on a VPS with Nginx and SSL
blogs

Telegram Bot Webhook vs Polling: Deploy grammY on a VPS with Nginx and SSL

getUpdates polling vs webhook for Telegram bots, then deploy a grammY webhook with Node.js, TypeScript, Nginx, Let's Encrypt SSL and systemd. Working code included.