Notion as internal tool builder
Notion
Notion is moving the automation budget upstream, from connecting many apps after the fact to building the workflow where teams already write, plan, and store data. Forms and database automations matter because they let an ops or marketing team collect inputs, update records, route work, and trigger follow ups inside the same workspace, which makes Notion feel less like a notes app and more like a lightweight internal tool builder.
-
Zapier and Make are strongest when a workflow jumps across many separate SaaS tools. Zapier sells app to app automation at scale, while Make goes deeper on visual logic and broader API endpoint coverage per app. Notion competes by collapsing the first layer of workflow into its own pages and databases, so fewer handoffs need an external orchestrator.
-
The real comparable is also Airtable, not just automation middleware. Airtable showed that a database with views, forms, and automations can become a custom app for marketing and ops teams. Notion approaches the same budget from the opposite direction, starting with docs and knowledge management, then adding databases, forms, and automations until a team can run the process without leaving the workspace.
-
This changes who buys Notion. A simple approval flow or intake system that once required Notion plus Zapier, or Airtable plus Zapier, can now be built by the team lead already administering the workspace. That strengthens land and expand dynamics, because every new workflow can pull in more seats and make the workspace harder to replace.
The next step is deeper execution, more triggers, richer integrations, and more polished interfaces for people who only need to submit or approve work. If Notion keeps turning pages and databases into operational software, it can win a larger share of internal workflow spend, while Zapier and Make become the tools used mainly when work must cross far beyond the Notion environment.