Both products finished our fictional request queue. Our chosen Make retry wrote one request twice after a lost reply. Keep the working Make route if you can make its writes safe; evaluate n8n if you must run the workflow engine yourself.
Recordings
Both routes saved the queue. The failure exposed the difference in our setups.
Can both save the same request queue?
Both saved the six valid requests and explained the invalid and repeated ones. The saved-result receipt confirms each queue row and disposition. The clips show the product histories and branches that led there.
Make40s clip
The existing Make route finished the baseline
Its history shows ordered runs. The saved receipt confirms six queue writes, one invalid request and one duplicate disposition. See saved result ↗
n8n17s clip
The n8n rebuild finished the baseline
The later walkthrough shows queue and duplicate branches. The saved receipt confirms six queue writes and the two non-queue dispositions. See saved result ↗
Limit of this test. The n8n clip reviews saved history after scoring. Neither interface clip alone proves every saved row; the in-page receiver receipt does.
Did the new rule affect only later requests?
Both sent the new urgent billing request to Finance Lead and kept earlier owners. The saved result has SR-108 assigned to Finance Lead, SR-109 to Duty and the earlier SR-104 still assigned to Duty.
Make67.833s clip
Make saved the new owner rule
The changed expression and two later runs are visible. The receiver receipt shows SR-108 as Finance Lead and SR-104 unchanged. See saved result ↗
n8n14s clip
n8n saved the rule and its later run
The labelled walkthrough shows the final expression, then saved run 10. The receipt supplies the Finance Lead row. See saved result ↗
Limit of this test. The n8n clip joins the final rule expression and a saved run from a later walkthrough. It does not film the edit or show the receiver owner field.
What happened when a write failed or lost its reply?
Both reached 12 dispositions. Make wrote SR-111 twice under its selected automatic retry; n8n stopped, then an inspected manual replay wrote it once. The first before-write fault left no row before repair. The lost reply was harder: the receiver had already saved SR-111 when the response failed.
Make59.375s clip
A successful Make run hid a repeated write
Make history shows the retry succeeding. The receiver ledger records two Finance queue writes for SR-111 after the first reply was lost. See saved result ↗
n8n15s clip
The n8n run stopped for an inspected replay
Saved run 14 shows the error and run 15 the repair path. The receiver ledger has one SR-111 queue write. See saved result ↗
Limit of this test. The products used different retry settings and repair steps against a fictional HTTP receiver. This test does not rank their general reliability.
Recommendations
Keep the working route until a specific requirement earns the rebuild.
Make
Keep Make for a working hosted route
Make finished our fictional job. Its chosen retry wrote one request twice after a lost reply. Check your real app for repeat writes. A verified need to run the engine could reverse this choice, but check eligibility.
n8n documents self-hosting. Our Cloud rebuild finished the same job. We did not test that deployment or time a move. Reconnect apps and check server upkeep. Keep Make if that work has no clear payoff.
Make presents a visual scenario builder for connecting apps and automating work in its managed cloud.
Visual scenariosManaged cloud on ordinary plans
What the pitch leaves out
Our chosen automatic retry finished with a successful run status after an uncertain reply, but wrote the same fictional request twice.
Keep the working route only with a write and repair design that suits the real destination.
Who runs the engine
Make runs ordinary scenarios in its cloud. A separate White Label/OEM on-premise route is documented, but this buyer's access and terms are unverified.
Work before relying on it
Check duplicate-write handling, destination credentials and the actual app actions in the existing scenario.
n8n
n8n offers a visual workflow editor through a managed Cloud plan or an instance you operate yourself.
Cloud workflow testedSelf-hosted route documented
What the pitch leaves out
Our Cloud workflow needed an inspected manual replay after the uncertain write. The test did not run a self-hosted instance or transfer an existing buyer workflow.
Budget for rebuilding and reconnecting the job; add server upkeep if you choose self-hosting.
Who runs the engine
n8n runs the tested Cloud workflow. Community and paid self-hosted editions let an eligible buyer operate an n8n instance. That route also makes the buyer responsible for server updates, backups and recovery, none of which our Cloud test measured.
Work before relying on it
Rebuild the routes, reconnect credentials, test the destination's failure behavior and, if self-hosted, operate the server.
Trade-offs
The rebuild changes who owns the workflow and its failures.
Your decision
Make
n8n
The same finished request queue
The existing Make scenario saved six valid baseline requests and two non-queue dispositions. Keeping it avoids an unmeasured rebuild, but its real app actions still need checking.
We rebuilt the route in n8n Cloud and got the same saved result. That proves this fictional HTTP job, not a direct Make blueprint import or a typical migration time. Saved fictional result · Make blueprints · n8n workflow import
After a write loses its reply
The configured automatic retry finished successfully but made two physical SR-111 writes. The run status alone hid the extra destination write.
The selected stop-on-error setting left a failed first run. After checking the saved destination, a manual replay wrote only the missing disposition, with one physical SR-111 queue write. Saved fictional result
Who operates the engine
Ordinary Make subscriptions run scenarios in Make's cloud. Make separately documents an on-premise White Label/OEM engine, but this buyer's access and terms are unverified.
n8n documents Community and paid self-hosted editions. Our observed workflow ran in n8n Cloud, so server operation and edition limits remain untested. Make White Label deployment · n8n self-hosted editions
What a saved run can replay
Make documents replaying an earlier trigger through the current scenario. That runs the current modules again and can repeat downstream writes.
n8n documents retries of failed executions and copying successful data into the editor. The exact completed-run production replay operation remains unverified in our source check. Make scenario replay · n8n execution debugging
What the plan meter counts
Make reports credits for module work. Our scored sequence used 46 credits, including its rule change and faults.
n8n reports workflow executions. Our scored sequence used 14 trial executions, including two failed first attempts and their manual replays. These units do not price the same workload. Make credits · n8n plans · Saved fictional result
Find your fit
Choose the condition that would justify rebuilding.
1Is your Make route already doing the job?
2Would you prefer to run the engine yourselves?
3Which saved-run action matters?
4How will you maintain workflow versions?
5Which target would you prefer to connect?
Pricing
The plan prices use different currencies and different units.
In our twelve-event fictional run, Make used 46 credits and n8n used 14 trial executions. Make counted module work; n8n counted whole workflow runs, including failed first tries. These units cannot yield a fair bill for a real buyer.
Commercial signals for Make and n8n. Make checked October 4, 2026; n8n checked October 4, 2026.
Commercial signals
make.com
n8n.io
Same for Make and n8n
Annual billing optionAvailable on published paid Cloud plans Make · n8n
Enterprise sales routeCustom quote through sales Make · n8n
Price basis
$ prices (ISO code unconfirmed)Per month, billed annually.Allowance measured in credits.The checked annual-payment selector displayed $ without an ISO currency code; the buyer's checkout currency and taxes were not verified.Make price source ·
€ prices (EUR)Per month, billed annually.Allowance measured in executions.EUR appeared in the checked region; n8n says the final billing currency follows the billing country at checkout.n8n price source ·
First plan allowance
Core $9 per month 10,000 credits per month selected; monthly price equivalent under annual payment. Hosted visual workflow builder Core credits reset monthly. The displayed $ has no verified ISO code.
Starter €20 per month 2,500 workflow executions per month; monthly price equivalent billed annually. Hosted visual workflow builder EUR appeared in the checked region. The final currency follows billing country.
Plan 2 allowance
Pro $16 per month 10,000-credit selector under annual payment; Pro receives an annual credit package. Hosted visual workflow builder Check the actual package and any variable-credit actions for your job.
Pro €50 per month 10,000 workflow executions per month; monthly price equivalent billed annually. Hosted visual workflow builder Check concurrency, saved-history and collaboration limits for your edition.
Plan 3 allowance
Teams $29 per month 10,000-credit selector under annual payment; Teams receives an annual credit package. Hosted visual workflow builder Team role and access needs can change the plan choice.
How much of the first paid plan would this route use?
Choose a duty and a monthly request count. We use the paths measured in our small fictional test to project credits and executions. The graph shows when each tool passes its first paid plan’s included use. It does not show a monthly bill.
What does the queue need to handle?
How many requests arrive each month?
Make
800credits projected
Published plan for context: Core, 10,000 credits, $9/month equivalent under annual payment. Price source ↗
8% of this first paid plan's limit, using the upper end of any range.
Below Core's 10,000 credits limit, but route fit remains unverified. The checked annual-payment selector displayed $ without an ISO currency code; the buyer's checkout currency and taxes were not verified.
n8n
202executions projected
Published plan for context: Starter, 2,500 executions, €20/month equivalent under annual payment. Price source ↗
8.08% of this first paid plan's limit, using the upper end of any range.
Below Starter's 2,500 executions limit, but route fit remains unverified. EUR appeared in the checked region; n8n says the final billing currency follows the billing country at checkout.
Share of each tool’s first paid plan limit
0–130% of each first paid plan limit
First paid plan limitMake8.08%n8n8.24%
One ownerRule changeRepairTwo owners
At 200 arrivals, we assume 192 valid requests, four invalid requests and four repeated IDs. These are chosen example counts, not a measured customer mix.
The two changed-rule checks add little use at this volume. The plan that permits the whole route is still unverified.
We measured this route with fictional requests on October 2. Repeating those paths for a month is an assumption. We haven't checked a real buyer's request mix, use at this volume, paid failed-run counting, plan access or a common billing currency. The published prices below are plan references, not bills for this example.
How published plan prices step upPublished monthly equivalents under annual payment. Each colored bar is scaled only within its own product’s listed plans; bar length does not compare currencies or work units.
Make
Core$9
10,000 credits per month selected; monthly price equivalent under annual payment.
Pro$16
10,000-credit selector under annual payment; Pro receives an annual credit package.
Teams$29
10,000-credit selector under annual payment; Teams receives an annual credit package.
Make counts credits; n8n counts executions. These prices do not show which product would cost less for the same work. These are monthly price equivalents under annual payment, checked 4 October. Make showed $ with no verified code; n8n showed EUR in this region. Taxes and outside-service fees are excluded. Self-hosted server work is unpriced. A real buyer’s usage is unmeasured.
Capabilities
The same checkmark can mean different access and setup.
48 differences77 unconfirmed42 no recorded differences
Make and n8n share much of the workflow work. Their code limits, data storage, replay and access rules differ. Check those limits before choosing a plan. A dash means we couldn’t confirm that exact operation.
A ✓ means available. Differences can be in availability, setup or limits. Unconfirmed answers are shown separately.
Capabilities of Make and n8n
Capability
Make
n8n
Build and change the workflow
Build in a visual editor(Ease of use was not tested.)
Arrange and connect workflow steps on a visual canvas.
✓
Make builds scenarios on a visual canvas. Add an app module with the plus control, configure its connection, and save the scenario. Connected apps and each selected module need their required accounts and permissions.
✓
Confirmed · Checked 2026-10-15
Connected apps and each selected module need their required accounts and permissions.
n8n builds workflows by adding and connecting nodes on its canvas. Built-in nodes provide app triggers, actions and data processing. A supported app account and credentials are required for external actions.
✓
Confirmed · Checked 2026-10-15
A supported app account and credentials are required for external actions.
Receive a webhook event(Delivery depends on webhook settings and limits; n8n has separate test and production URLs.)
Start a workflow when an HTTP webhook receives an event.
✓
Make creates a custom webhook URL that starts a scenario when the sending service posts data. Configure the webhook and activate the scenario. Incoming requests use webhook queues and service limits.
✓
Confirmed · Checked 2026-10-15
Incoming requests use webhook queues and service limits.
n8n uses Webhook to receive HTTP events and start a workflow. Test and production URLs differ. Production registers after publishing. Caller must use the intended URL and configured authentication.
✓
Confirmed · Checked 2026-10-15
Caller must use the intended URL and configured authentication.
n8n uses Schedule Trigger for fixed intervals or calendar times. Save and publish the workflow and set the intended timezone. Workflow must be saved and published. Uses workflow timezone, otherwise instance timezone.
✓
Confirmed · Checked 2026-10-15
Workflow must be saved and published. Uses workflow timezone, otherwise instance timezone.
Route an item by a condition(Make routes process sequentially; n8n Switch may use the first or every matching output.)
Send an item down a branch chosen by its values.
Make’s router processes routes in sequence. n8n’s Switch can send to the first or all matching outputs.
Different setup
✓
Make uses a Router with a filter on each route to send bundles down matching paths. Routes run in order. A fallback handles unmatched data. Router routes run sequentially, not in parallel.
n8n uses the If node for true/false branches and Switch for more outcomes. Configure comparison rules for the values being checked. The comparisons must match the incoming data types.
✓
Confirmed · Checked 2026-10-15
The comparisons must match the incoming data types.
n8n: Visual data transformation nodes support the no-code claim; expressions are JavaScript-like and are not counted as no-code here. The specific contact trim and effort remain untested.
✓
Confirmed · Checked 2026-10-02
Visual data transformation nodes support the no-code claim; expressions are JavaScript-like and are not counted as no-code here. The specific contact trim and effort remain untested.
Run JavaScript or Python in a step(Make Code needs a paid plan and charges by run time; n8n library access depends on hosting.)
Execute JavaScript or Python inside a workflow step.
Make Code needs a paid plan and charges for runtime. n8n’s library access depends on Cloud or self-hosting.
Different limits
✓
Make Code runs JavaScript or Python in a workflow module. Its built-in editor supports completion and error highlighting. Paid Make plan. Runtime, memory and library limits depend on plan. Custom libraries require Enterprise.
✓
Confirmed · Checked 2026-10-15
Paid Make plan. Runtime, memory and library limits depend on plan; custom libraries require Enterprise.
Make uses an Iterator to split an array into individual bundles, then runs the following modules for each bundle. Input must be an array. Downstream app limits still apply.
✓
Confirmed · Checked 2026-10-15
Input must be an array; downstream app limits still apply.
Make attaches notes to modules or routes for instructions and explanations. Open note markers or the notes panel to read them. Notes are not included when a scenario is cloned or shared by link.
✓
Confirmed · Checked 2026-10-15
Notes are not included when a scenario is cloned or shared by link.
Scenario inputs can be required and typed; Make validates collection fields against their specification. This does not validate every external payload automatically.
✓
Confirmed · Checked 2026-10-04
Scenario inputs can be required and typed; Make validates collection fields against their specification. This does not validate every external payload automatically.
n8n: The reviewed input-definition guide does not establish automatic type and required-field validation for every incoming workflow payload; add explicit checks for the particular route.
—
Not confirmed · Checked 2026-10-04
The reviewed input-definition guide does not establish automatic type and required-field validation for every incoming workflow payload; add explicit checks for the particular route.
Save code that can be called from multiple workflows.
Unconfirmed
✓
On Make Enterprise, a Team Admin creates a JavaScript function in Functions. Team members can reuse it in scenarios. Functions must run synchronously within 300 ms and cannot make HTTP requests or use external libraries.
✓
Confirmed · Checked 2026-10-15
Enterprise; Team Admin creates or edits, Team Members can use. Synchronous JavaScript only; no HTTP or external libraries.
When building a custom connector, fetch selectable field options from its service.
✓
Make: Custom app authors use a dynamic-options RPC to populate a select field from the service API. This is connector development, not a setting on every supplied app.
✓
Confirmed · Checked 2026-10-04
Custom app authors use a dynamic-options RPC to populate a select field from the service API. This is connector development, not a setting on every supplied app.
n8n: Custom node authors define methods.loadOptions to query a service and render returned choices; node installation and service authentication are separate.
✓
Confirmed · Checked 2026-10-04
Custom node authors define methods.loadOptions to query a service and render returned choices; node installation and service authentication are separate.
Read a stored knowledge file’s descriptive fields for later steps.
Unconfirmed
✓
Make: Knowledge → Get knowledge returns name, description, date and ID for a selected knowledge file. This does not promise arbitrary file-format metadata extraction.
✓
Confirmed · Checked 2026-10-04
Knowledge > Get knowledge returns name, description, date and ID for a selected knowledge file. This does not promise arbitrary file-format metadata extraction.
Make: Data stores support record operations, but a comparable multi-record update/delete operation is not established in this guide; iteration is a separate route.
—
Not confirmed · Checked 2026-10-04
Data stores support record operations, but a comparable multi-record update/delete operation is not established in this guide; iteration is a separate route.
n8n: A published production Webhook trigger starts the workflow when another program sends an HTTP request. This is not a direct run endpoint in the workflow-management API.
✓
Confirmed · Checked 2026-10-04
A published production Webhook trigger starts the workflow when another program sends an HTTP request. This is not a direct run endpoint in the workflow-management API.
Make AI Agent (New) is in open beta, with paid access for custom providers. n8n’s documented Agent node is a workflow component with separate model credentials.
Different limits
✓
Make: AI Agent (New) chooses connected tools; open beta can change.
✓
Confirmed · Checked 2026-10-04
AI Agent (New) chooses connected tools; open beta can change.
n8n: Basic status/time filters documented; saved custom-data filters are plan/edition-limited. Full-text payload search is not established by this yes.
✓
Confirmed · Checked 2026-10-02
Basic status/time filters documented; saved custom-data filters are plan/edition-limited. Full-text payload search is not established by this yes.
Replay a completed run from its triggerEarlier published note: (Make reruns all current modules and uses credits. The exact n8n production replay operation is unverified.)
Start the current workflow again with saved trigger data from a completed run.
Unconfirmed
✓
Make can replay old trigger data through all current modules on every plan, using current variables and credits. Retention limits and repeat writes apply. No-data polling checks and isolated non-trigger module runs are excluded.
✓
Confirmed · Checked 2026-10-02
All plans can replay old trigger data through every module of the current scenario, using current variables and consuming credits; retention and repeated writes matter. Poll checks with no data and isolated non-trigger module runs are excluded.
n8n: Self-hosted pruning settings control saved execution data; Cloud plan retention differs. Cloud Enterprise also lists extended retention; a plan entitlement differs from self-hosted configuration.
✓
Confirmed · Checked 2026-10-04
Self-hosted pruning settings control saved execution data; Cloud plan retention differs. Cloud Enterprise also lists extended retention; a plan entitlement differs from self-hosted configuration.
n8n: Workflow creator/editor exists in sharing scope; distinct Project Editor is Cloud Pro or self-hosted Enterprise and Project Viewer is Cloud/self-hosted Enterprise. Registered Community project/RBAC docs conflict with the edition page.
✓
Confirmed · Checked 2026-10-02
Workflow creator/editor exists in sharing scope; distinct Project Editor is Cloud Pro or self-hosted Enterprise and Project Viewer is Cloud/self-hosted Enterprise. Registered Community project/RBAC docs conflict with the edition page.
Keep workflow versions in GitEarlier published note: (Make CLI may work alongside Git, but built-in Git control is unverified; n8n requires Business or Enterprise.)
Connect workflow versions to a Git repository.
Unconfirmed
Unconfirmed
Whether Make can connect workflow versions to a Git repository remains unconfirmed.
Evidence and history
Not confirmed · Checked 2026-10-15
Whether Make can connect workflow versions to a Git repository remains unconfirmed.
Original comparison: Unconfirmed · 2026-10-02.
Source details haven’t been published for this answer.
✓
n8n: Git source control requires Business/Enterprise and administrator setup.
✓
Confirmed · Checked 2026-10-02
Git source control requires Business/Enterprise and administrator setup.
Let another person reuse the same configured agent.
Unconfirmed
Unconfirmed
Make: The new-agent guide establishes creation and scenario tools, but does not confirm a colleague’s direct reuse of the same agent independently of scenario access.
—
Not confirmed · Checked 2026-10-04
The new-agent guide establishes creation and scenario tools, but does not confirm a colleague’s direct reuse of the same agent independently of scenario access.
n8n shares published agents within a project for use by workflows and sub-agents. Preview covers all Cloud plans; self-hosting needs setup and excludes Enterprise. A public share link remains unconfirmed.
✓
Confirmed · Checked 2026-10-04
Published agents are project artifacts available to users and callable from that project’s workflows or sub-agents. Preview: Cloud all plans; self-hosted requires setup and excludes Enterprise. This does not promise a public share link.
Package a starting workflow so it can be loaded for another build.
Make has in-product templates on all plans. n8n’s cited route submits a workflow to its library or serves a custom library on self-hosted instances; it does not establish the same private-template editor.
Different limits
✓
Make: Anyone can create a scenario template on all plans; community-app templates cannot be publicly published.
✓
Confirmed · Checked 2026-10-04
Anyone can create a scenario template on all plans; community-app templates cannot be publicly published.
n8n: Shared workflow editors can edit it; credential access can limit some nodes. Cloud all plans, self-hosted Business/Enterprise; no simultaneous-editing claim.
✓
Confirmed · Checked 2026-10-04
Shared workflow editors can edit it; credential access can limit some nodes. Cloud all plans, self-hosted Business/Enterprise; no simultaneous-editing claim.
n8n: The credential guide establishes personal credential placement, not privacy of every workflow. Workflow privacy for this exact space is not confirmed.
—
Not confirmed · Checked 2026-10-04
The credential guide establishes personal credential placement, not privacy of every workflow. Workflow privacy for this exact space is not confirmed.
Use the vendor-hosted platform(n8n Cloud Starter and Pro are hosted; Business is self-hosted only.)
Build and run workflows on infrastructure operated by the vendor.
Make subscriptions run on vendor infrastructure. n8n Cloud Starter and Pro are hosted; Business is self-hosted.
Different limits
✓
Make’s scenario service creates and runs scenarios on its documented production zones, including eu1.make.com; ordinary access is through the hosted service. Separate White Label access is not implied.
✓
Confirmed · Checked 2026-10-02
Make’s scenario service creates and runs scenarios on its documented production zones, including eu1.make.com; ordinary access is through the hosted service. Separate White Label access is not implied.
Run the workflow engine on your own infrastructureEarlier published note: (Make White Label/OEM has a separate on-premise engine, but ordinary subscriber access is unverified. Its on-prem agent is a network connector.)
Install and operate the workflow engine on infrastructure you control.
Unconfirmed
Unconfirmed
Whether Make can install and operate the automation platform on infrastructure under your control remains unconfirmed.
Evidence and history
Not confirmed · Checked 2026-10-15
Whether Make can install and operate the automation platform on infrastructure under your control remains unconfirmed.
Original comparison: Unconfirmed · 2026-10-02.
Source details haven’t been published for this answer.
✓
Self-host n8n using Docker or another supported deployment method, then configure it for your infrastructure. You handle maintenance; features differ across Community, Business and Enterprise editions.
✓
Confirmed · Checked 2026-10-15
Self-hosted Community, Business and Enterprise editions have different features.
Connect a cloud workflow to a private networkEarlier published note: (Make’s on-prem agent is Enterprise-only. A general n8n Cloud private-network route is unverified.)
Let a vendor-hosted workflow reach a service on a private network.
Unconfirmed
✓
Make: Enterprise On-prem agent gives cloud scenarios access to local HTTP/API systems; target fit untested.
✓
Confirmed · Checked 2026-10-02
Enterprise On-prem agent gives cloud scenarios access to local HTTP/API systems; target fit untested.
Whether n8n can let a vendor-hosted workflow reach a service on a private network remains unconfirmed.
Evidence and history
Not confirmed · Checked 2026-10-15
Whether n8n can let a vendor-hosted workflow reach a service on a private network remains unconfirmed.
Original comparison: Unconfirmed · 2026-10-02.
Source details haven’t been published for this answer.
View billable usage for a runEarlier published note: (Make shows credits per run. n8n’s per-run billed status and failed-run quota treatment remain unresolved.)
See the chargeable usage units attributed to one saved run.
Unconfirmed
✓
Make: Credit usage table shows credits per scenario run on all plans.
✓
Confirmed · Checked 2026-10-02
Credit usage table shows credits per scenario run on all plans.
For self-hosted n8n, set instance options in the deployment’s environment or .env file and restart the service. For Docker Compose, pass the values into the n8n service. Protect secrets and check the option’s supported version.
✓
Confirmed · Checked 2026-10-15
Self-hosted deployment configuration. Restart when the option requires it.
Make: The current RabbitMQ app guide lists Send to Exchange and Send to Queue, but does not establish a native receive-message trigger. This does not rule out other broker or custom-app routes.
—
Not confirmed · Checked 2026-10-04
The current RabbitMQ app guide lists Send to Exchange and Send to Queue, but does not establish a native receive-message trigger. This does not rule out other broker or custom-app routes.
The finished queue is real for this test. The move still needs checking.
One fictional HTTP job on two accounts
Both ran twelve fictional events on 2 October: Make Core and an n8n Cloud trial. Each saved twelve dispositions. Make used 46 credits; n8n used 14 executions. The n8n video shows saved history, not live scoring. Saved result · Make credits · n8n plans
A lost reply after the destination wrote
The same injected fault reached different repair procedures. Make automatically retried and committed SR-111 twice. n8n stopped after the lost reply, then an inspected manual replay added the missing disposition without another queue write. Neither result proves a general reliability rate. Saved fictional result
Move and handover
We rebuilt the route; we did not time a real move. Each tool exports its own JSON. No colleague reconnected or fixed our route. We did not test a self-hosted n8n server or a real app. Make blueprint guide · n8n import guide · n8n self-hosting guide
Other product limits to check
Before you commit
Both routes need a recovery rule for an uncertain write.
Make’s
The selected automatic retry repeated a physical queue write.
The Make run finished successfully while the receiver held two Finance writes for SR-111. This concerns our chosen scenario and fictional destination.
Keep the route if it serves the job, but verify how the real destination handles a lost reply before relying on automatic retry.
n8n’s
The selected stop-on-error path required manual inspection.
The first n8n execution failed after the receiver saved SR-111. A checked replay added only the missing disposition. Our test used Cloud.
Evaluate self-hosting for an actual control requirement, then test the edition, server duties, credentials and repair path.
Four limits to carry into your own test.
The destination was a fictional HTTP receiver. A completed HTTP write does not prove the same result in your CRM, spreadsheet or email service.
The n8n clips show saved history after scoring. The published receiver receipt establishes saved rows and physical writes; the later walkthrough does not film live submissions.
We did not measure a typical migration time. Build, edit, repair, reconnection and independent handover time remain open for a real buyer.
The two displayed price lists do not make a common bill. Make showed an unlabelled $ and counts credits; n8n showed EUR in this region and counts executions. Checkout and hosting costs vary.
Start with one real destination and a small, finished result. Check what was already written before replaying a failed step. An export is a setup record, not a working connection.
From readers
What did your repair leave in the destination?
If you have run the same job in both products, share the plan, destination, failed step, saved result and who repaired it. Leave out client details and credentials.
Signing in, commenting and sending your answers on all need JavaScript. Everything above this line doesn’t.
Sign in to say something
We send one link and you click it. No password, ever. Signed in, your answers up the page come back next time.
We read every comment before it shows. Plain text, and we publish it as you wrote it.
They get a link that opens this page with your answers already in, plus your username. We don’t carry a message.