Guide · name an owner
Who should own your automations
Name who owns the desk before you pick a product. Totals are not published yet. Self-hosted is a separate lane. A score is not an owner. This page does not add new scores.
Name an owner, or leave it vague
Name
Name an owner if…
The job is live or about to ship. Someone must publish a change, reconnect a login, get paged when it fails, and take the job if the first person is out or leaves. You can write that name down — and a cover person who can do the same work.
Vague
Leave it vague if…
You still need to know whether the job is worth automating — that is What’s worth automating. The hub is unnamed — Name one system of record for small-team ops (Notion, Airtable, or Superhuman Docs (formerly Coda)). You are chasing a run that still looks on — When automations look fine. You want what sticks when you switch — What does not migrate. You want which product to buy — that is the picker. This page names a person. It does not rank products.
A name-an-owner or leave-it-vague check for one desk.
- You need to name who reconnects, gets paged, and takes the job if that person leaves.
- You will pick an operator, a builder, or engineering.
Read more
What this page tells you. Help a small team name who owns automations day-to-day — who is accountable, and who is left if that person is out — before picking Make, n8n, or Zapier. An operator, a builder, or engineering. Then which tool lane fits. This page does not reprint the four-question flowchart, the silent-breakage checklist, the residue list, or the name-the-hub read. It adds no score cells. Dated list prices live on the picker after you name the owner.
GuideSome scores not shown yetVendor and community pages accessed 2026-09-17Live scorecard
This page is not a tool pick
The question here is who owns the desk. Whether the process is ready lives on What’s worth automating. Whether the hub is named lives on Name one system of record for small-team ops. A run that still looks on lives on When automations look fine. What sticks when you switch lives on What does not migrate between Zapier, Make, and n8n. How to run both copies lives on How to run old and new automation side by side. Which product to use lives on Which automation tool for small teams — this page does not reprint that flowchart. This page does not reprint those reads. It does not rank tools. It does not add new scores.
This page also skips a list-price table. The question is who is accountable — not which plan to buy. After you name the owner, dated official list prices live on the picker. This page does not claim you will save money, and it does not invent a monthly dollar from a /500 score.
What “own” means on this desk
Own is a name, not a product setting. If only one person can publish, reconnect, or restore the box, that person is the owner — whether you wrote it down or not. Sharing a connection is not the same as naming who acts when it expires.
Accountable
A person you can page
Who publishes a change. Who holds the login. Who clicks Reconnect. Who gets the failed run. Write those names before the job is live.
Cover
Who is left if they are out
A cover person who can do the same work on vacation or at 2am. If nobody else can reconnect, the first person is still the only owner.
Transfer
Who takes the job when they leave
Change owner, move the workflow, or keep the connection on a team mailbox you still control. Removing a user is not a transfer.
Three ownership lanes
Name the person first. Then pick the product. Totals are not published yet. This page does not add a score. After you name the owner, pick a tool with four questions — not this page’s table: Which automation tool for small teams. Name the hub first: Name one system of record for small-team ops.
Operator
Non-technical operator
Zapier’s quick start is “without code.” The operator can publish a Zap this week. The runtime stays in vendor cloud. The work that stays on the desk is reconnects, not Docker. Zapier: Reconnect is only available for connections you own. When you turn on or publish a Zap, the Zap owner must have access to every app connection used in it. If the person who connected the app leaves and nobody else owns that connection, the Zap can stop. That is a named person, not a 2am server page.
- Build or change. The operator publishes and edits. A cover person must be able to do the same.
- Credentials and reconnects. Share the connection before vacation. Only the owner can click Reconnect.
- Incidents and decommission. A failed or paused Zap pages the operator. Change owner before someone leaves.
Honest cases: When Zapier is still the right pick. Make can still fit an operator who will map modules — When Make is the right pick.
Source: Zapier — Zap workflows quick start guide · Zapier — manage your app connections · Zapier — Zap owner must have every connection · accessed 2026-09-17
Builder
Semi-technical builder
The builder maps modules on Make’s visual canvas. The runtime stays in vendor cloud. OAuth 2.0 connections grant access for a limited time — Make says you may need to reauthorize periodically. If verification fails, Reauthorize; if that fails, create a new connection. AccountValidationError happens during initialization and cannot be caught by an error handler. Consecutive errors disable scheduling. Make Community: a contractor left, the connection stayed under their email, and the scenario failed to verify. Team connections are shared — still name who reauthorizes.
- Build or change. The builder maps modules. A Team Operator can start or stop a schedule — that is not the same as owning the mapping.
- Credentials and reconnects. All users on the team can use connections created on that team. Name who created them.
- Incidents and decommission. A disabled schedule pages the builder. Removing a user from a team is not a transfer.
A technical builder who will use n8n’s editor without running a box is still this side of the line — n8n Cloud, not self-host. Honest cases: When Make is the right pick.
Source: Make — connect an application · Make — fix errors and warnings · Make Community — how to troubleshoot connection issues · Make — teams · Make Community — scenario failed after the contractor left · accessed 2026-09-17
Engineering
Eng-owned
n8n’s choose-how page splits two jobs: Cloud (n8n manages hosting, updates, and scaling) versus self-hosted (you control the environment). Cloud is the technical builder desk — vendor-hosted, no box. Self-host is the only desk where engineering owns the box. n8n’s Docker Compose guide is for expert users: servers, containers, scaling, and security. If you are not experienced at managing servers, n8n recommends n8n Cloud. Community: a wrong volume path (/root/.n8n instead of /home/node/.n8n) lost data on update. A corrupted config file lost the encryption key; stored credentials could not be recovered. 2am on self-host pages you.
- Build or change. The engineer changes workflows and the host. A cover person must be able to pull and restart.
- Credentials and reconnects. Credentials live in a project the cover person can open. Moving a credential revokes sharing.
- Incidents and decommission. Wire an Error Trigger. Persist the volume. Store the encryption key off the box. Delete a project only after you transfer or delete its workflows on purpose.
Honest cases: When n8n self-host is worth it. n8n Cloud stays on the picker — not this lane.
Source: n8n — choose how to use n8n · n8n — use Docker Compose · n8n Community — Docker update lost data and the encryption key · n8n Community — lost config file, credentials unrecoverable · accessed 2026-09-17
The ops burden that stays after the demo
Cloud is not “no owner.” Self-host is not “a cheap licence.” A product does not assign these names. Write who takes each job:
- Build or change authority. Who can publish a Zap, save a Make scenario, or edit an n8n workflow — and who can do that when the first owner is out. Zapier: Change owner transfers the Zap to another user in the account. Make: scenarios belong to a team; a Team Operator can activate or stop a schedule but is otherwise read-only. n8n: workflow owners can move a workflow to another user or project.
- Credentials. Who holds the login, API key, or OAuth grant. Zapier connections are private until you share them. Make: all users on the team can use and manage connections created on that team — still name who created them. n8n stores credentials in a personal space or a project; moving a credential changes ownership and removes existing sharing.
- Reconnects. Zapier: only the connection owner can click Reconnect. Make: reauthorize OAuth, or replace the connection. n8n Cloud: the builder re-enters credentials. Nobody named means the next expiry is a silent stop. Product compare: Error handling across Make, n8n, and Zapier.
- Incident response. Vendor cloud pages the vendor for the runtime. The team still pages a person for a failed Zap, a disabled Make schedule, or a broken n8n node. n8n: set an error workflow in Workflow Settings; it must start with the Error Trigger. Self-host pages you for the box and the job. If the run still looks healthy, see When automations look fine — this page does not reprint that checklist.
- Vacation or 2am coverage. Name a cover person before the owner is out. Zapier: share the connection; if you stop sharing, a published Zap that needs it pauses. Make: the cover person must sit on the same team. n8n: the cover person must reach the project and the Error Trigger. If the instance dies overnight and no one is named, do not ship self-host. If a Zap or scenario dies and no one is named, do not ship that job yet — see What’s worth automating.
- Decommissioning. Write who takes the job when someone leaves. Zapier Team or Enterprise: remove a member and transfer their Zaps and connections — Catch Hook URLs can change, and you choose whether private connections last 30 days or until they expire. Make: connections stay on the team; deleting a connection can stop every scenario that uses it. n8n: move the workflow and credentials, or delete the project after you choose transfer or delete.
- Docker / VPS. Only the eng-owned self-host lane. Persist
/home/node/.n8n. StoreN8N_ENCRYPTION_KEYoff the box. A dump without the key is not a restore.
Source: Zapier — manage your app connections · Zapier — manage assets (change Zap owner) · Zapier — remove members and transfer ownership · Make — connect an application · Make — teams · n8n — organize work in projects · n8n — handle errors gracefully · n8n — set a custom encryption key · accessed 2026-09-17
If that person is out
This is who is left — not whether the run still looks on. False-green symptoms stay on When automations look fine — this page does not reprint that checklist. What stays behind when you switch stays on What does not migrate.
- The contractor’s email still holds the connection. Make Community: a contractor left, the connection stayed under their email, and the scenario failed to verify. Team connections are shared — still name who created them and who reauthorizes.
- Only the Zapier connection owner can click Reconnect. If that person is on leave, or has left, a published Zap that needs the connection can pause. Share the connection before vacation. Change owner before someone leaves.
- The encryption key lives on one laptop. n8n self-host: a dump without
N8N_ENCRYPTION_KEYis not a restore. Community threads show a lost key leaving stored credentials unrecoverable. Store the key off the box, and name who can use it at 2am. - Nobody else can publish a change. A Team Operator who can start or stop a Make schedule is not the same as a person who can edit the mapping. A cover person must be able to do the owner’s job, not only see the history.
Source: Make Community — scenario failed after the contractor left · Zapier — share app connections · Zapier — Zap owner must have every connection · n8n Community — lost config file, credentials unrecoverable · accessed 2026-09-17
Ownership checklist
Who does the work, who is accountable if it fails, who covers vacation or 2am. Fill every row before you ship. A lane that “usually owns” a product is not a crown. Tools do not assign these names for you.
Swipe sideways on a narrow screen. Not a scored table.
| Job | Operator-owned | Builder-owned | Eng-owned |
|---|---|---|---|
| Build or change the job | The operator publishes and edits. No unnamed contractor. | The builder maps modules or nodes. A named deputy can save. | The engineer changes workflows and the host. Not a hope. |
| Hold the credentials | Connection owner is the operator — or a shared team mailbox they still own. | Team connections are shared. Still name who created them. | Credentials live in a project the cover person can open. |
| Reconnect or reauthorize | Only the Zapier connection owner can click Reconnect. | Reauthorize OAuth, or replace the Make connection. | Re-enter credentials. Self-host also owns the encryption key. |
| Incident response | Failed Zap, On hold, or a paused workflow — a named inbox. | Disabled Make schedule or a failed n8n Cloud run — a named person. | Error Trigger plus the box. 2am pages you. |
| Vacation or 2am cover | A cover person who can reconnect and turn the Zap back on. | A cover person who can reauthorize and restart the schedule. | A cover person who can restore the volume and the key. |
| Decommission or transfer | Change Zap owner before someone leaves. Catch Hook URLs can change. | Scenarios and connections stay on the team. Remove is not a transfer. | Move the workflow and credentials, or delete the project on purpose. |
- Named owner for each live job.
- Named cover person who can reconnect without waiting.
- Credentials not sitting on a departing contractor’s email.
- An incident path that pages a person — not only a green icon.
- A written transfer before someone leaves.
Source: Zapier — share app connections · Zapier — remove members and transfer ownership · Make Community — scenario failed after the contractor left · n8n — create and edit credentials · n8n — organize work in projects · accessed 2026-09-17
Tool fit by ownership lane
Ownership first, then the product. This is not a new score. Totals are not published yet. Four questions after you name the owner: Which automation tool for small teams — this page does not reprint that flowchart.
Operator / builder
Zapier for operator or builder desks
Usually the operator-owned lane: a first Zap this week, a catalog need, or a set of Zaps the operator already runs. A builder can still own Zapier when the mapping stays simple. It does not make the operator optional. Honest cases: When Zapier is still the right pick.
Operator / builder
Make for operator or builder desks
Usually the builder-owned lane: visual modules, credit volume you can count, no box. An operator who will map modules can still own Make. Team connections are shared — still name who reauthorizes. Honest cases: When Make is the right pick.
Technical builder
n8n Cloud for a technical builder
Same n8n editor family, vendor-hosted. n8n manages hosting, updates, and scaling. That is not engineering-owned ops. You still name who edits nodes, holds credentials, and gets the Error Trigger. Four questions: Which automation tool.
Eng-owned only
n8n self-host only if engineering owns the box
Self-host is the only engineering-owned box. It is not a fourth cloud seat. If you will not run Docker or a VPS and own 2am, stay on Cloud, Make, or Zapier. Honest cases: When n8n self-host is worth it.
Decision table
Who builds, who gets paged, and whether you will run the box. This is ownership — not the four-question picker. Next reads stay on the still-right and self-host pages. If nobody is named, the automations only look fine — catch silent breakage and false-green runs on When automations look fine.
Swipe sideways on a narrow screen. Not a scored table.
| Who builds | Who gets paged | Cloud vs self-host | Next read |
|---|---|---|---|
| Non-technical operator | The operator — expired connections and failed Zaps | Vendor cloud only. No Docker or VPS. | — When Zapier is still the right pick |
| Semi-technical builder | The builder — reauthorize, credit errors, disabled schedules | Vendor cloud only. No box to run. | — When Make is the right pick |
| Technical builder (vendor-hosted editor) | The builder — nodes, credentials, failed runs | Cloud. You will not run the box. | — Which automation tool |
| Engineer who will run the box | The engineer at 2am — host, backups, and jobs | Self-host. Docker or a VPS you keep running. | — When n8n self-host is worth it |
| Nobody named | Nobody. The job will fail quietly. | Cloud or self-host does not matter yet. | When automations look fine — catch silent breakage |
A lane that usually owns a product is not a crown. When the current setup already works, stay until you can name the savings in each vendor’s own unit. When Zapier is still the right pick · When Make is the right pick · When n8n self-host is worth it · When automations look fine — catch silent breakage and false-green runs.
After you name the owner
The person is named. Use the sibling that owns the next job — without treating this page as a ranking.
- Job still not worth automating: What’s worth automating — and what to leave manual.
- Hub still unnamed: Name one system of record for small-team ops.
- A run still looks on: When automations look fine — catch silent breakage · When automations fail — name the class first · Error handling across Make, n8n, and Zapier.
- Switching tools: What does not migrate between Zapier, Make, and n8n · Parallel-run before you switch.
- Count units before a plan: How to meter automation.
- Four questions, then a pick: Which automation tool for small teams.
Primary CTA stays the live scorecard. This button is the next read after the owner is named.
Scoring status
Scoring status
The live card is Make vs n8n vs Zapier. Totals are not published yet.
When-to-pick copy lives on Make vs n8n vs Zapier — when to pick each. Pair reads: Make vs n8n · Make vs Zapier · n8n vs Zapier. Scoring rules: Methodology.
Product links
Sources
Primary vendor pages and community threads. Access date for every citation on this page: 2026-09-17. We do not invent search volumes, weekly ops-hour claims, testimonials, review-site counts, or a converted list.
- Zapier — Zap workflows quick start guide · accessed 2026-09-17
- Zapier — manage your app connections · accessed 2026-09-17
- Zapier — share app connections · accessed 2026-09-17
- Zapier — Zap owner must have every connection · accessed 2026-09-17
- Make — connect an application · accessed 2026-09-17
- Make — fix errors and warnings · accessed 2026-09-17
- Make Community — how to troubleshoot connection issues · accessed 2026-09-17
- Make Community — scenario failed after the contractor left · accessed 2026-09-17
- n8n — choose how to use n8n · accessed 2026-09-17
- n8n — use Docker Compose · accessed 2026-09-17
- n8n — set a custom encryption key · accessed 2026-09-17
- n8n Community — Docker update lost data and the encryption key · accessed 2026-09-17
- n8n Community — lost config file, credentials unrecoverable · accessed 2026-09-17
- Zapier — manage assets (change Zap owner) · accessed 2026-09-17
- Zapier — remove members and transfer ownership · accessed 2026-09-17
- Make — teams · accessed 2026-09-17
- n8n — create and edit credentials · accessed 2026-09-17
- n8n — organize work in projects · accessed 2026-09-17
- n8n — handle errors gracefully · accessed 2026-09-17
FAQ
Who should own automations on a small team?
Name a day-to-day owner before you pick a tool. A non-technical operator usually owns Zapier. A semi-technical builder who will map modules usually owns Make. A technical builder who will use n8n’s editor without running a box owns n8n Cloud. n8n Self-host is only for engineering that will run Docker or a VPS and take 2am. This page does not cite a total. It adds no cells.
Name an owner, or leave it vague?
Name an owner if the job is live or about to ship, and someone must publish, reconnect, get paged, and take the job if the first person is out or leaves. Leave it vague if you still need to know whether the job is worth automating, the hub is unnamed, you are chasing a run that still looks on, or you want which product to buy. This page names a person. It does not rank products.
Does this page replace the four-question picker?
No. This page is who owns the desk. The picker is tool choice: who builds, volume shape, self-host willingness, catalog need. After you name the owner, use Which automation tool for small teams. This page does not reprint that flowchart.
What does each owner still owe after the demo?
Who can publish a change, who holds the logins, who reconnects, who gets paged, who covers vacation or 2am, and who takes the job when someone leaves. Cloud is not “no owner.” A product does not assign those names. Use the checklist on this page before you ship.
What does a non-technical Zapier owner still have to do?
Vendor cloud keeps the runtime off your desk. The operator still owns expired connections. Zapier: Reconnect is only available for connections you own. When you publish a Zap, the Zap owner must have access to every app connection used in it. If the person who connected the app leaves, the Zap can stop. That is not a 2am server page — it is still a named person.
Is n8n Cloud owned by engineering?
No. n8n Cloud is a technical-builder desk: vendor-hosted editor, no Docker or VPS. n8n manages hosting, updates, and scaling. You still name who edits nodes, holds credentials, and gets the Error Trigger. Self-host is the only desk where engineering owns the box.
What happens if nobody owns n8n self-host at 2am?
Then self-host is the wrong pick. n8n recommends self-host for expert users. Community threads show a wrong Docker volume path losing data on update, and a lost encryption key leaving stored credentials unrecoverable. It is not a fourth cloud seat. Honest cases: When n8n self-host is worth it. If a job still looks healthy but nobody is paged, see When automations look fine.
Do Zapier, Make, or n8n guarantee ownership if someone leaves?
No. Sharing a connection is not a named owner. Zapier can transfer a Zap and its connections when you remove a Team or Enterprise member — Catch Hook URLs can change, and private connections may expire. Make connections belong to a team; a contractor who leaves can still be the email on the connection. n8n can move a workflow or credential; moving revokes sharing. Write the transfer before someone leaves.
Does this page change the Make vs n8n vs Zapier scores?
No. Totals are not published yet. It is not a fourth cloud seat. This guide adds no cells and no new rank. Rules live on Methodology. Commissions do not move a score.
Affiliate disclosure
Product links on this page: n8n and Zapier stay official-site URLs with UTM only — no invented IDs. Make Partner (pc=stackscorecard) is live elsewhere on the site and is not the primary call here. Rankings are not sold. Wordmarks are not partnership marks. Policy: Affiliate disclosure · Disclosures. Commissions do not move a score, a weight, or a pricing cell.