n8n vs Make: templates compared for buyers
This guide is for people who want to buy a ready-made automation for n8n or Make rather than build one. It does not rank the two platforms. It explains how a template reaches you on each, where it runs, and what to check before you pay.
The platform you already use is usually the right one. If you are choosing, the practical questions are where you want the automation to run and which apps it has to connect.
The two platforms in one paragraph each
n8n is a workflow automation tool where a workflow is a graph of nodes. It can be self-hosted on your own server or used as a hosted service, and workflows are stored as JSON.
Make (formerly Integromat) is a cloud automation service where an automation is a scenario made of modules. A scenario can be exported as a JSON blueprint.
Side by side
What you buy: | n8n: A workflow, as a JSON file | Make: A scenario, as a blueprint (JSON file)
How you bring it in: | n8n: Import from file or URL, or paste into the editor | Make: Import the blueprint into a new scenario
Where it runs: | n8n: On your own server, or on n8n’s hosted service | Make: On Make’s cloud
Your accounts: | n8n: You create your own credentials | Make: You create your own connections
Usage is measured in: | n8n: Executions on hosted plans; your own server limits when self-hosted | Make: Operations, under your plan
Hosting: the main structural difference
n8n can be self-hosted, which means you run it on infrastructure you control and are responsible for updates, backups and security. It is also available as a hosted service. Make and Zapier are cloud services only, so there is nothing to install or maintain, but your automations run on their platform under your plan’s limits.
What to check before buying an n8n template
Which n8n version the seller tested on, and whether your version has the nodes the workflow uses.
Whether it needs community nodes, and whether your setup lets you install them.
The list of credentials you will need to create.
Whether sub-workflows are included, and the order to import them in.
Whether it was tested self-hosted, on n8n’s hosted service, or both.
What to check before buying a Make template
The apps and modules used, and whether you have accounts for each.
The operations a typical run uses and the scheduling interval, then compare with your plan.
Any data store, data structure or webhook you must set up yourself.
Which fields you must re-map to your own spreadsheets, bases or channels.
Listings on this marketplace by platform
Live counts of published listings in each platform category.
Counts only describe how many listings exist, not how good they are. Before you buy any listing, read its description, requirements and reviews, and check the refund terms: requests are reviewed case by case, and for standard products they must be made within 14 days of purchase.
- n8n workflows 208 listings
- Make.com templates 29 listings
Choosing between them
If you want to run automations on your own server, n8n is the one of the two that supports it. If you prefer a managed service with nothing to host, Make is a cloud service. Beyond that, choose by the apps you need to connect and by what your team already uses, because a template only helps if you can run it.