Guide · name the hub
Name one system of record for small-team ops
Name one hub on the workspace scorecard — Notion, Airtable, or Superhuman Docs (formerly Coda) by the object people open tomorrow. Different criteria from the automation scorecard. Self-hosted is a separate lane. This page does not add new scores.
Use this page, or skip it
Use
Use this if…
You have not named the one object people will edit tomorrow — the page, record, or table row — and you are about to wire Make, n8n, or Zapier. Status, owner, and the current row should live in one place. Automations may write that hub. They are not a second tracker.
Skip
Skip if…
You already named the hub and want to know if the job is worth automating — that is What’s worth automating. You want to count units — How to meter automation. You want to run old and new side by side — How to run old and new automation side by side. You want which of Notion, Airtable, or Superhuman Docs is the better pick for a named object — those are the pair pages. This page names the hub. It does not rank products.
A name-the-hub or skip check for one ops job.
- You need one named hub before you wire Make, n8n, or Zapier.
- You will pick Notion, Airtable, or Superhuman Docs (formerly Coda) as that hub.
- You want the workspace sheet, which uses different criteria from the automation scorecard.
Read more
What this page tells you. Help a small team name one system of record for ops work — before wiring Make / n8n / Zapier on top of chaos. One write path. Automations wait until that hub is named. It does not reprint the pass-or-defer audit, the meter, the side-by-side switch, or the pair pages. It adds no score cells. Dated list prices live on the pair pages after the object is named.
GuideSome scores not shown yetVendor pages accessed 2026-09-17Workspace scorecard
Coda is now Superhuman Docs (Jul 2026). Source: Superhuman — What’s changing: Coda becomes Superhuman Docs.
This page is not a tool pick
The question here is whether the hub is named. Whether the process is ready lives on What’s worth automating. What to watch on the meter lives on How to meter automation. How to run old and new at the same time lives on How to run old and new automation side by side. When a run fails, name the class on When automations fail. Which of Notion, Airtable, or Superhuman Docs fits a named object lives on the pair pages. Which automation product to use lives on Which automation tool for small teams. 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 which object people edit tomorrow — not which plan to buy. After the hub is named, dated official list prices live on Notion vs Airtable · Notion vs Superhuman Docs · Airtable vs Superhuman Docs. This page does not claim you will save money, and it does not invent a monthly dollar from a /500 score.
What a system of record means for ops
For ops, the system of record is one named object people edit — and one write path into it. Status, owner, and the current row live there. Automations may read it, write it, and notify. They are not a second tracker. Name that object before you pick Make, n8n, or Zapier.
Write path
One object, one edit
People open the same page, record, or table row tomorrow. A second Sheet, a second base, or a chat pin for the same job is a second write path pretending to be backup.
Automations
Runs write the hub
A Make scenario, a Zap, or an n8n execution writes where you point it. The run is not the record. If the team still edits a copy, the green history is about the copy.
Owner
Someone names the row
Who edits structure, who edits rows, and who gets paged when a run looks fine but the hub is stale. See Who should own your automations.
Sources: Notion — intro to databases · Airtable — linking records · Superhuman Docs — overview: tables · accessed 2026-09-17
What belongs in the system of record vs automations
The system of record is the one hub people edit. Automations read it, write it, and notify. They are not a second tracker. Work the list in order. If a step fails, stay manual — see What’s worth automating — then come back.
- 1. Name the object of record. A Notion database item is a page. An Airtable hub is records linked across tables. A Superhuman Docs hub is a table inside a doc. Pick the object people will open tomorrow. Coda became Superhuman Docs on 8 Jul 2026 — a new name is not a new hub. Sources: Notion — intro to databases · Airtable — linking records · Superhuman Docs — overview: tables · Superhuman — What’s changing: Coda becomes Superhuman Docs · accessed 2026-09-17
- 2. One hub for the same job. Status, owner, and the current row live in one place. A Sheet, a second base, and a Notion page for the same job is three systems of record pretending to be one.
- 3. What belongs in the system of record. The live record. Who owns it. The fields operators edit. The view they trust. Native in-hub edits that finish inside that workspace.
- 4. What belongs in automations. Multi-app writes, a CRM or helpdesk the hub cannot finish, a webhook fan-out, and a designed failure path. Native Notion, Airtable, and Superhuman Docs automations can stay in the hub when the work ends there. Sources: Notion — database automations · Airtable — getting started with automations · Superhuman Docs — automations · accessed 2026-09-17
- 5. Name the owner. Who edits structure, who edits rows, and who gets paged when a run looks fine but the hub is stale. See Who should own your automations.
- 6. Then pick the automation tool. Only after the hub is named. Open Which automation tool for small teams or the automation scorecard. This page does not rank tools and adds no score cells.
When there is no one hub
These are operator patterns, not an industry share. We do not invent a percent, a review count, or a converted list. No system of record shows up as duplicate sources and false-green automations — the run looks fine while the hub is stale.
- Two hubs for the same job. Notion holds the brief. Airtable holds the tracker. A Sheet holds “the real numbers.” Nobody can say which row is current. That is two write paths, not a backup.
- Duplicate sources. The same status is typed into email, a page, and a base. A Make, n8n, or Zapier job that “syncs all three” encodes the mess. Name one object first.
- Automations writing to a copy. Make, n8n, or Zapier updates a shadow table. The team still edits the old page. The run can look fine while the system of record is stale — a false-green. See When automations look fine and Error handling across Make, n8n, and Zapier.
- Each person keeps a private tracker. Chat pins and personal pages drift. The named hub is empty by Friday.
- No owner for the hub. Views, fields, and native automations change without a named person. Reconnects have nowhere to go.
Fix the hub before you add another scenario. A new automation tool does not name the record.
When to stay in Notion, Airtable, or Superhuman Docs
Stay means this product is the system of record. The pair pages name when each object fits. They are not a second trio. This page does not duplicate the full workspace scorecard.
Swipe sideways on a narrow screen. Not a scored table.
| If the daily object is | Candidate | Next read |
|---|---|---|
| A page people write in, next to the records | Notion — docs-plus-database hub | Notion vs Airtable for small-team ops hubs · Notion vs Superhuman Docs (formerly Coda) for small-team wikis and docs |
| Linked records and a named view, not the raw table | Airtable — relational base hub | Notion vs Airtable for small-team ops hubs · Airtable vs Superhuman Docs (formerly Coda) for small-team ops hubs |
| A table inside one doc, with Packs in that doc | Superhuman Docs — one living doc | Notion vs Superhuman Docs (formerly Coda) for small-team wikis and docs · Airtable vs Superhuman Docs (formerly Coda) for small-team ops hubs · Coda is now Superhuman Docs — stay, or move to Airtable / Notion? |
Stay
When to stay in Notion
Writing lives with the records. Every database item is a page. In-workspace edits, Slack, or Gmail finish the job. Not a reason to pick Notion for every job.
Notion vs Airtable for small-team ops hubs · Notion vs Superhuman Docs (formerly Coda) for small-team wikis and docs · When Notion automations are enough — and when to hand off
Stay
When to stay in Airtable
The source of truth is a relational base: linked records, named views, an interface without the raw table. Still the hub when the base is the object.
Notion vs Airtable for small-team ops hubs · Airtable vs Superhuman Docs (formerly Coda) for small-team ops hubs
Stay
When to stay in Superhuman Docs
The hub is one living doc: tables in the doc, Packs in that doc, Doc Makers you can name. Still the hub when the doc is the object. Coda became Superhuman Docs on 8 Jul 2026. A new name is not a new hub.
Notion vs Superhuman Docs (formerly Coda) for small-team wikis and docs · Airtable vs Superhuman Docs (formerly Coda) for small-team ops hubs · Coda is now Superhuman Docs — stay, or move to Airtable / Notion?
Sources accessed 2026-09-17. Notion pages: Notion — intro to databases. Airtable views: Airtable — getting started with views. Superhuman Docs Packs: Superhuman Docs — overview: use Packs.
When automations should wait
Automations wait until the hub is named, the write path is one, and someone owns a miss. Native Notion, Airtable, and Superhuman Docs automations can stay in the hub when the work ends there. Make, n8n, or Zapier wait until that call is made. When those tools appear, totals are not published yet. It is not a fourth cloud seat.
Swipe sideways on a narrow screen. Not a scored table.
| Situation | Wait | Next read |
|---|---|---|
| The object of record is unnamed | Yes. Do not encode three copies. | This page — name the hub first. |
| Two hubs hold the same job | Yes. Pick one write path. | Notion vs Airtable for small-team ops hubs · Airtable vs Superhuman Docs (formerly Coda) for small-team ops hubs |
| The work finishes in the hub | Stay native. Do not add Make, n8n, or Zapier for an in-workspace edit. | When Notion automations are enough — and when to hand off |
| Nobody owns reconnects or a paused run | Yes. A green history with no owner is a false-green waiting to happen. | Who should own your automations · Error handling across Make, n8n, and Zapier |
| The job still fails the pass-or-defer audit | Yes. Leave it manual until the path is lean and written. | What’s worth automating — and what to leave manual |
| Hub named; the same event must write other apps | No — then pick the automation tool. The hub stays the write target. | Notion automation limits — when to hand off to Make · Which automation tool for small teams |
What the vendors actually run
- Notion. Database automations are trigger-and-action sequences on a database. Full automations sit on paid plans. They will not act on restricted pages, and they cannot be triggered by other automations. A failed run can pause until someone sets it Active again. Formula and webhook issues may not notify you.
- Airtable. An automation is a trigger plus one or more actions — native to the base or integrated. Only Owner/Creator can create or configure; Editors can view the configuration. Airtable counts a run when a trigger fires, including failed attempts, and publishes monthly run limits by plan. This page does not invent a monthly dollar from those limits.
- Superhuman Docs. Automations live in the doc. Packs install per doc, not across the workspace. Automations that take actions as Automation Bot can be edited by anyone with edit access; run as yourself is owner-locked. Name that owner before you rely on the run.
- Make, Zapier, n8n. Make calls the build a scenario: modules run in sequence when an event hits the first module. A Zap is a trigger plus one or more actions; you map fields so each run writes the value from that event. n8n counts an execution as one run of a workflow. None of those objects is the system of record.
Source: Notion — database automations · Airtable — getting started with automations · Superhuman Docs — automations · Make — what’s a scenario · Zapier — what is a Zap · n8n — understand executions · accessed 2026-09-17
After you name the hub
The system of record is named. Now pick how work leaves the hub — or stay native.
- Notion stays in-workspace: When Notion automations are enough — and when to hand off.
- Notion event, other apps: Notion automation limits — when to hand off to Make.
- Pass or defer the job first: What’s worth automating — and what to leave manual.
- Count units before a plan: How to meter automation.
- Run old and new side by side: Parallel-run before you switch.
- Name who owns reconnects: Who should own your automations.
- What a green run actually means: When automations fail — name the class first · Error handling across Make, n8n, and Zapier · When automations look fine — catch silent breakage.
- Then pick Make, n8n, or Zapier: Which automation tool for small teams.
Primary CTA on this page stays the workspace scorecard. This button is the next read after the hub is named.
Scoring status
Scoring status
Workspace card. Live card: Notion vs Superhuman Docs (formerly Coda) vs Airtable. Different criteria from the automation scorecard.
Totals are not published yet. Live card: Make vs n8n vs Zapier.
Scoring rules: Methodology.
Product links
Official
Notion
Official site: Notion · no affiliate ID · not a partner mark
Official
Airtable
Official site: Airtable · no affiliate ID · not a partner mark
Official
Superhuman Docs
Official site: Superhuman Docs (formerly Coda) · no affiliate ID · not a partner mark
n8n and Zapier are named only for the after-hub picker. Totals are not published yet. Official sites: n8n · Zapier · no affiliate ID.
Sources
Primary vendor pages. Access date for every citation on this page: 2026-09-17. Totals are not published yet. We do not invent search volumes, testimonials, G2 or Capterra counts, industry percents, or a converted list. Sprawl stays qualitative.
- Notion — intro to databases · accessed 2026-09-17
- Notion — database automations · accessed 2026-09-17
- Airtable — linking records · accessed 2026-09-17
- Airtable — getting started with views · accessed 2026-09-17
- Airtable — getting started with automations · accessed 2026-09-17
- Superhuman Docs — overview: tables · accessed 2026-09-17
- Superhuman Docs — overview: use Packs · accessed 2026-09-17
- Superhuman Docs — automations · accessed 2026-09-17
- Superhuman — What’s changing: Coda becomes Superhuman Docs · accessed 2026-09-17
- Make — what’s a scenario · accessed 2026-09-17
- Zapier — what is a Zap · accessed 2026-09-17
- n8n — understand executions · accessed 2026-09-17
FAQ
What is a system of record for small-team ops?
The one hub people edit for a job: current status, the row or page, and who owns it. One write path. Automations read and write that hub. They are not a second tracker.
What does a single write path mean?
Status, owner, and the current row live in one named object. People open that object tomorrow. Make, n8n, or Zapier may write it — they do not become a second hub. A Sheet, a Notion page, and Slack pins for the same job is three write paths.
What are the symptoms of no system of record?
Two hubs for the same job, an automation writing to a copy while the team edits the old page, private trackers that empty the named hub, and no owner for views or reconnects. A green run on the copy is a false-green — the run looks fine while the hub is stale. See When automations look fine and Error handling across Make, n8n, and Zapier.
Should I pick Make, n8n, or Zapier before I name the hub?
No. Name the system of record first. Wiring Make, n8n, or Zapier on top of two trackers copies the mess. After the hub is named, pick a tool on Which automation tool for small teams. Totals are not published yet.
When should automations wait?
Wait when the object of record is unnamed, two hubs hold the same job, nobody owns reconnects, or the job still fails the pass-or-defer audit. Native in-hub edits can stay in Notion, Airtable, or Superhuman Docs (formerly Coda). What’s worth automating is the audit. Who should own your automations names the person.
Can Make, n8n, or Zapier be the system of record?
No. A Make scenario, a Zap, or an n8n execution is a run that writes where you point it. The hub is still the Notion page, Airtable record, or Superhuman Docs table people edit. Those tools stay on a separate sheet — not comparable to the workspace card.
Notion vs Airtable vs Superhuman Docs — which should be the system of record?
It depends on the object people open tomorrow. Notion if writing lives with the records. Airtable if the hub is a relational base. Superhuman Docs (formerly Coda) if the hub is one living doc with Packs. Longer compares: Notion vs Airtable, Notion vs Superhuman Docs, Airtable vs Superhuman Docs. The trio card is Notion vs Superhuman Docs vs Airtable. This page does not duplicate that sheet.
What do I do after I name the system of record?
If the hub is Notion and the work stays in-workspace, see When Notion automations are enough. If the same event has to run other apps, see the Notion to Make handoff, then Which automation tool for small teams. Name who owns reconnects. Pass or defer the job before you build. Count units on How to meter automation. A side-by-side switch lives on How to run old and new automation side by side before you switch.
Affiliate disclosure
Product links on this page: Notion, Airtable, Superhuman Docs (formerly Coda), 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.