Resources · Zapier integration

Notion Zapier integrationAutomate Notion with Zapier.

The Notion Zapier integration brings 6 triggers, 15 actions and 11 searches: react to new rows, edits and comments, then write pages, blocks and files back into Notion. What each step costs, what breaks, and your first Zap.

See the 32 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Notion Zapier integration actually does

Connecting Notion to Zapier lets a change in your workspace start work in other apps, and lets other apps write into Notion without anyone copying and pasting. Zapier sits in the middle: it waits for one event, then runs the steps you lined up behind it. No code, but a few settings decide whether the Zap ever sees your pages.

A live intake table. Form answers, leads or support requests become rows through Create Data Source Item, and New Data Source Item passes each new row to the next tool.

Pages that build themselves. Create Page, Add Block to Page and Upload File to Page or Block turn a meeting, a deal or a delivery into a ready page with its files attached.

Status changes that speak up. Updated Properties in Data Source Item notices a status or a date moving, and Add Comment leaves the note right where the team reads it.

A word on vocabulary: a data source is the table inside a Notion database, and one database can hold several. What Zapier does not do here: it never sees a page or database that has not been shared with the integration you signed in with, and it does not pick up anything created before the Zap was switched on. If you also weigh other tools, read the Notion n8n integration and the Notion Make integration pages before you commit.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English, once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does once it has started: the step that writes, sends or changes something in an app on your behalf.
Task
The unit Zapier bills: one action your Zap completes successfully. The number printed on your plan counts those.
Polling vs instant
A polling trigger is checked on a timer by Zapier. An instant trigger is reported by the app itself, the moment the event happens.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and quietly stops it otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can reuse what it found.
Cost

What a Notion Zap really costs

Watching Notion is free: the trigger never costs a task, and Notion is not a premium app, so it works on the free plan.

  • Trigger0 tasks, whatever the volume
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo, free plan accepted

Each action that succeeds counts as one task, and a failed one is not counted. Every action is billed on its own, so a three-action Zap eats three times more than a one-action Zap. The free plan stops at two steps, one trigger and one action. Add a filter, a search such as Find Page (By Title) or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid only concerns polling triggers; all six Notion triggers are instant, so it never applies to them.

Connect

Connect your Notion workspace in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Notion account linked to Zapier once, then reused by every step that reads or writes in Notion.

  2. 02

    Pick Notion

    Type Notion in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the Notion sign-in screen, where the next step happens.

  3. 03

    Sign in and grant access

    Log in to the workspace your Zaps will use and grant Zapier access. Pages and databases you do not own need read or write access on the Notion side, or Zapier will not reach them.

First Zap

Your first Notion Zap

GoalEvery new request added to a Notion intake table that meets your rule gets its own working page, created automatically.

  1. 01

    Create the Zap

    Start a new Zap and pick Notion as the app that starts it. Choose New Data Source Item as the event, then select the connection you made earlier.

  2. 02

    Pick the data source

    Select the intake table in the Data Source field, which is required. Test it: Zapier brings back the three most recent rows, so you map fields on a real request.

  3. 03

    Add the filter

    Click the plus icon, add Filter, then set the field, the rule and the value. A text rule only works on text. The filter turns this into a multi-step Zap, which needs a paid plan.

  4. 04

    Add the action

    Add Notion again and choose Create Page. Pick the parent page that will hold the new pages, then map what you want to carry over from the request.

  5. 05

    Test, then publish

    Run each step once and read what came back before going further. When the test page shows up under its parent, click Publish to switch the Zap on.

Triggers

Notion triggers

6 events start a Zap when something happens in Notion, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Comment

Instant trigger

In Zapier“Triggers when a new comment is created in your Notion workspace. You can filter by database or specific page.”

Fires as soon as someone posts a comment in your Notion workspace, and you can narrow it to one database or one page.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
feedback left on a product spec should reach the person who owns that spec, in the tool they actually check.
Watch out
left wide open, every comment in the workspace starts the Zap, so narrow it to the database or page that matters before it eats your tasks.
2

New Data Source Item

Instant trigger

In Zapier“Triggers when a new item is created in a data source.”

Starts the Zap each time a row is added to the data source you pick. It is the trigger behind most intake tables, from form answers to support requests.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a new lead or a new request lands in your tracking table and should open a ticket or a message somewhere else.
Watch out
Data Source is required, and if yours is not in the list, its database has not been shared with the integration you connected with. Share it first, then refresh.
3

Updated Content in Data Source Item

Instant trigger

In Zapier“Triggers when the content in a data source item is updated.”

Reacts when the body of a row changes: the text and blocks written inside the item, not its properties. Use it when the writing itself is what matters.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a draft in your content calendar gets reworked, and the editor wants to hear about it without refreshing the page all day.
Watch out
a change of status or date does not count here, it belongs to the properties trigger below. Pick the right one before testing, or the Zap stays silent.
4

Updated Properties in Data Source Item

Instant trigger

In Zapier“Triggers when one or more properties of a data source item are updated.”

Fires when one or more properties of a row change, such as a status, an owner or a due date.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a project row moves to done, and the client or the finance team should be told without anyone writing an email.
Watch out
if the same Zap then edits that row with Update Data Source Item, the change sets the trigger off again. Add a filter or the loop burns tasks fast.
5

Updated Content in Page

Instant trigger

In Zapier“Triggers when the content in a page is updated.”

Keeps an eye on one page you choose and fires when what is written on it changes. Handy for reference pages that people should not miss an edit on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your onboarding guide or internal policy page gets edited, and the people who rely on it should get a heads-up.
Watch out
the Page field is required and only lists pages shared with the integration you signed in with. A missing page means a missing share, not a broken Zap.
6

Updated Properties on a Page

Instant trigger

In Zapier“Triggers when one or more properties of a page are updated.”

Fires when properties change on the single page you pick. It suits a page that works like a record, with fields that matter to someone else.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a client page carries a stage field, and each change of stage should be logged or announced elsewhere.
Watch out
on a standalone page, outside any database, paste its Page ID by hand, and only changes to the Title property are detected there.
Actions

Notion actions

Notion gives you 15 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Block to Page

Action

In Zapier“Adds a new content block to an existing Notion page. Supports various block types including paragraphs, headings, lists, to-dos, callouts, code blocks, and more.”

Drops one new block into an existing page: a paragraph, a heading, a list item, a to-do, a callout, a code block and more. You pick the type in Block Type.

When to use it
each new task from another tool becomes a to-do line on a shared checklist page.
Watch out
Page and Block Type are both required; for a to-do, the Checked field decides whether it arrives already ticked.
2

Archive Data Source Item

Action

In Zapier“Soft deletes an item in a data source.”

Archives a row, a soft delete: the item leaves the table but can be brought back later with the restore action below.

When to use it
a lead marked as lost in your CRM should disappear from the active pipeline table.
Watch out
keep the row's ID somewhere, such as a field in another tool, because restoring asks for it.
3

Add Comment

Action

In Zapier“Adds a new comment to a Page.”

Posts a new comment on a page, so the note appears where your team already works instead of in yet another inbox.

When to use it
a payment arrives or a document gets signed, and the matching page should say so in a comment.
Watch out
a row of a data source is a page too, but it still has to be shared with your integration before Add Comment can reach it.
4

Create Data Source Item

Action

In Zapier“Creates an item in a data source.”

Adds a new row to a Notion data source, filled with values mapped from earlier steps. It is the workhorse for turning outside events into a table you can sort and filter.

When to use it
every new form answer or signed deal should land as a row in your tracking table.
Watch out
the data source must be shared with your integration, or it will not appear in the list.
5

Create Page

Action

In Zapier“Creates a Page inside a parent page”

Creates a page inside a parent page you choose. Good for documents that do not belong in a table, such as meeting notes or a brief.

When to use it
a meeting booked in your calendar should come with a notes page ready before anyone joins.
Watch out
the new page lives under its parent, so pick a parent the integration can write to.
6

Add Content to Page

Action

In Zapier“Adds Content to a Page.”

Adds content to a page that already exists. Lighter than building block by block when you just want more text on the page.

When to use it
a running log page collects one entry per closed ticket or per call summary.
Watch out
Page is required, and only pages shared with the integration you signed in with show up.
7

Restore Data Source Item

Action

In Zapier“Restores a data source item which was previously archived.”

Brings back a row that was archived earlier, so it reappears in its data source with its content.

When to use it
a deal marked as lost comes back to life and its row should return to the table.
Watch out
the Item ID of the archived row is required, so carry it from an earlier step or paste it.
8

Update Database

Action

In Zapier“Updates a Notion database attributes including title, parent location, inline display, icon, archive status, and lock status.”

Edits the database itself rather than its rows: title, location, inline display, icon, trash status and lock. It is a housekeeping action more than a daily one.

When to use it
a project closes and its database should be locked against edits in the Notion app.
Watch out
the dropdown only lists databases with a single data source; for one that has several, paste the database ID instead.
9

Update Data Source Item

Action

In Zapier“Updates a data source item.”

Changes the properties of an existing row: move a status, set a date, assign an owner. The row is picked in the Item field.

When to use it
a payment received in your billing tool should flip the matching project to paid.
Watch out
run it from a Zap triggered by that same data source and you build a loop; a filter on the trigger keeps it in check.
10

Update Data Source Schema

Action

In Zapier“Updates a Notion data source schema including properties and title. Allows adding, modifying, or removing data source properties to change the schema.”

Changes the structure of a data source: its title and its properties, which you can add, modify or remove. Think column changes, not row changes.

When to use it
a template workspace is cloned for each client and needs one extra property added every time.
Watch out
Data Source is required, and only data sources whose database is shared with your integration show up, so share it first.
11

Upload File to Data Source Item

Action

In Zapier“Uploads a file to a files property in a data source item.”

Puts a file into a files property of a row, taken from an earlier step or from a public link. Invoices, contracts and photos end up attached to the right record.

When to use it
a signed contract from your e-signature tool should sit on the client's row.
Watch out
only properties that accept files are offered; with custom input, type the property name exactly as Notion shows it.
12

Upload File to Page or Block

Action

In Zapier“Uploads a file to a page or block in Notion.”

Attaches a file directly to a page or a block, rather than to a database property. The file comes from an earlier step or a public link.

When to use it
a recording or a slide deck should appear inside the meeting page that discusses it.
Watch out
you can pick the page from the dropdown or map a page or block ID from another step; File is required too, from an earlier step or a public link.
13

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced action that sends a raw request to Notion with your connection's sign-in already attached. It covers whatever the ready-made steps leave out.

When to use it
someone on the team knows the Notion API and needs one call with no dedicated action.
Watch out
requests only reach Notion's own domains, and Stop on error decides whether a failed call halts the Zap.
14

Retrieve Database

Action

In Zapier“This action retrieves a database in Notion using the ID of the database.”

Fetches a Notion database from its ID and hands its details to the next steps. Despite sitting among the actions, it reads rather than writes.

When to use it
a later step needs the database's details, and only its ID travelled with the trigger.
Watch out
it works from an ID, so you need to carry that ID from an earlier step or paste it.
15

Retrieve a Page

Action

In Zapier“This action retrieves a specific page from Notion using its ID. The page id can be a normal page or a database item. https://developers.notion.com/reference/retrieve-a-page”

Pulls one page from Notion by its ID, whether it is a plain page or a row of a database. Another read-only step listed with the actions.

When to use it
the trigger only gave you a page ID and the next step needs the page's properties.
Watch out
the ID must point to a page shared with your integration, or nothing comes back.
Searches

Notion searches

11 search steps look for data that already exists in Notion, so a later step can use it.

A search step finds something that already exists in Notion and hands it to the following steps. Notion has eleven of them. Three settings decide what happens when the answer is not the one you expected.

1

Retrieve Block Children

Search

In Zapier“Retrieves the children of a block, with any text content rendered as Markdown.”

Reads what sits inside a block and returns its text as Markdown, ready to drop into a text field elsewhere.

When to use it
you want the written body of a page sent into an email or a document elsewhere.
Watch out
it returns the content of one block's children, so point it at the right parent.
2

Get Page Comments

Search

In Zapier“Retrieves comments from a Page.”

Collects the comments on one page so a later step can quote or count them.

When to use it
a weekly summary of the discussion on a decision page should go to people who never open Notion.
Watch out
the Page field is required and only offers pages shared with your integration.
3

Find Data Source Items

SearchFind or create

In Zapier“Searches for items in a data source by its properties.”

Looks for rows in a data source by the values of their properties, such as an email or a client name. Its find-or-create variant, Find or Create Data Source Item, is the same search with the creation box ticked, not a separate operation.

When to use it
before adding a contact, check whether that person already has a row.
Watch out
without find-or-create, a search that finds nothing stops the Zap by default.
4

Get Block

Search

In Zapier“Retrieves a block by ID.”

Fetches a single block by its ID, for when you need one precise piece of a page rather than all of it.

When to use it
a status callout at the top of a page should be read and passed on.
Watch out
Block ID is required; you can copy it from the block's link or map it from another Notion step.
5

Get Block Children

Search

In Zapier“Retrieves child blocks of a parent block or page with support for pagination.”

Lists the child blocks of a block or page, page after page when there are many. Use it when you need the blocks themselves, not a Markdown rendering.

When to use it
a checklist page should be read item by item so each line can be handled.
Watch out
Block ID is required and can be a page ID as well.
6

Get Page and Children

Search

In Zapier“Retrieves a page by its ID and all of its block children.”

Grabs a page and every block under it in one go. One step instead of chaining a page lookup and a block lookup.

When to use it
a full brief page should be archived or copied into another tool, content included.
Watch out
the Page ID is required, so it has to travel from an earlier step or be pasted.
7

Get Page or Data Source Item by ID

Search

In Zapier“Retrieves a specific page or data source item from Notion using its ID.”

Finds a page or a row by its ID, whichever of the two it turns out to be, and returns it to the Zap.

When to use it
another tool stored the Notion ID of a record and you need its current values back.
Watch out
the ID can come from the page's link or from another step; a typo returns nothing.
8

Find Page (By Title)

Search

In Zapier“Searches for a page by title.”

Searches pages by their title, the way you would type it into Notion yourself.

When to use it
a client's name arrives from your CRM and the Zap needs that client's page to write into.
Watch out
two pages with the same title both match, so the multiple-results setting above decides which one wins.
9

Get Page Property

Search

In Zapier“Retrieves a specific property value from a Notion page.”

Reads one property value from one page, nothing more. Lighter than pulling the whole page when a single field is enough.

When to use it
a message should quote the due date of a project without mapping every other field.
Watch out
Page and Property are both required, and the page must be shared with your integration.
10

Query Data Source (Advanced)

Search

In Zapier“Query a Notion data source with advanced filtering and sorting using JSON. Supports complex logic like AND/OR conditions, multiple sorts, and all Notion filter types.”

Queries a data source with advanced filters and sorting written in JSON, with AND and OR logic and every Notion filter type. Power users only.

When to use it
the simple search cannot express a rule such as overdue and unassigned and high priority.
Watch out
the query is written by hand, so one misplaced bracket breaks it; test before publishing.
11

Get User Details

Search

In Zapier“Retrieves user information by ID.”

Returns information about a Notion user picked from the list, so later steps can use their name or details.

When to use it
a row assigns an owner and the notification should address that person properly.
Watch out
if expected users are missing from the list, check the permissions of the connected account.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there, and the steps relying on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for the fields needed to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a Notion Zap breaks

Most Notion failures on Zapier are not bugs. They come from sharing settings in Notion and from how Zapier treats triggers and searches.

Zapier keeps help articles on Notion, including one on common problems and one on the message below about searches. The six cases below come from those articles, the field help of the Notion steps and Zapier's general limits. When a Zap stops anyway, the Zapier troubleshooting guide walks through the next checks.

  • The page is not in the dropdown

    Notion only shows Zapier what has been shared with the integration you signed in with. Share the page or the database, then refresh the field.

  • Nothing could be found for the search

    A Notion search came back empty, so by default the Zap stopped there. Check the value you searched for, or switch on the setting that lets the Zap carry on.

  • Standalone page, title only

    Updated Properties on a Page only detects Title changes on a page outside any database. Other fields moving there will not start the Zap.

  • A Zap that restarts itself

    Watch a data source for property changes and update that same data source in an action, and each run sets off the next one, burning tasks fast.

  • Old rows are never picked up

    A Zap only reacts to what happens after you switch it on. Rows and pages that already existed stay untouched; moving them is a separate job.

  • Flood protection after an import

    When a trigger suddenly returns a huge batch, after a bulk import or a migration into Notion, Zapier's flood protection can hold it back.
Need help

Need help automating Notion with Zapier?

A person reads every message.

FAQ

Notion and Zapier: common questions

01Is the Notion Zapier integration free?
Yes, it runs on the free plan, because Notion is not a premium app. The free plan gives 100 tasks a month, an unlimited number of Zaps, and Zaps of two steps: one trigger and one action. That covers a lot with Notion, like turning each new form answer into a row. The ceiling appears as soon as you add a filter, one of the eleven searches or a second action: the Zap becomes multi-step and needs a paid plan. No price is given here, since Zapier changes its grid often.
02How many tasks does a Notion Zap use?
One per action that succeeds, and nothing for the trigger. A Zap that watches New Data Source Item and runs one action costs one task per new row. Two actions double that, three triple it. An action that fails is not counted. The thing to watch is the property triggers: every status change, every date moved, every owner reassigned starts the Zap again. On a busy table, a filter that only lets through the changes you care about keeps the count down, at the price of making the Zap multi-step.
03Are Notion triggers on Zapier instant?
Yes, all six of them. New Comment, New Data Source Item and the four update triggers are instant: Notion tells Zapier as soon as the event happens, so the Zap starts right away. The interval grid of the plans, 15 minutes on Free, 2 on Professional and 1 on Team and Enterprise, only applies to polling triggers, and Notion has none on Zapier. A free account reacts as fast as an Enterprise one. In the editor, a Zap built on an instant trigger shows a lightning bolt next to it.
04What does connecting Notion to Zapier require?
A Notion account, plus read or write access on any page or database you do not own and want a Zap to touch. The connection itself is quick: open Apps in Zapier, click + Add connection, pick Notion, then sign in and grant access in the tab that opens. The step people miss comes after: each page and database must be shared with the integration you signed in with. Until it is, it simply does not appear in Zapier's dropdowns, which looks like a bug but is not.
05Why is a Notion page missing from the Zapier dropdown?
Because it has not been shared with the integration your connection uses. The help text of almost every Notion field on Zapier says the same: if the expected page or data source is not there, check that it is shared with the same integration you authenticated with. A second case affects Update Database: its dropdown only lists databases with a single data source, so one holding several needs its ID pasted instead. In both cases the Zap is fine, the fix is on the Notion side.
06What if the Notion operation you need is missing?
Start with API Request (Beta). It sends a raw request to Notion with the sign-in of your connection already attached, so nobody handles credentials by hand. It does need someone at ease with the Notion API documentation, since you set the method and the address yourself, and requests can only go to Notion's own domains. Before going that far, check Query Data Source (Advanced): its JSON filters cover a lot of cases that the simpler searches cannot express. For a single missing call, that usually beats switching tools.
07Zapier, Make or n8n for Notion?
It depends on criteria, not on a winner. Setup effort: Zapier gets a Notion flow running from a guided editor. Cost model: Zapier bills every successful action as a task, so a busy table with frequent property changes adds up, and the other two bill in their own way, worth checking before you compare. Coverage: on Zapier, Notion offers six instant triggers, fifteen actions and eleven searches. If your flow needs something outside that list, read the Make and n8n pages for this app first.
Same platform

Other docs you might need on this stack.

Browse all integrations