Resources · Make integration

Notion Make integrationAutomate Notion with Make.

Your workspace can do more than wait for someone to update it. The Notion Make integration puts 32 modules, the bricks of a Make automation, in your hands: create pages, update items, read blocks. No code, and no plugin to install.

Try the Notion integration on MakeSee the 32 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Notion Make integration actually do?

Make is a place where you chain apps together. A scenario is the automation you build there: a first module watches Notion or another app, the next ones act. With Notion connected, those modules create pages, fill items in a data source, read the blocks written on a page, and hand the result to whatever comes next in the chain.

Three shapes cover most of what teams build here. A page for every new item: Watch Data Source Items spots the row that just landed in your roadmap table, Create a Page writes the brief that goes with it. A workspace that fills itself: a form, a mailbox or another tool feeds Create a Data Source Item, and the table nobody keeps current stops being a problem. Notion as the source: Search Objects and List Page Contents pull what is already written, and the rest of the chain sends it out.

What Make will not do is guess. The connection, your Notion account linked to Make once and reused by every Notion module, only reaches the pages you ticked when you granted access, and widening that list means building a new connection. On the Notion side, a page object stops at 25 property references, which is exactly why List Page Property Items exists: when a module answers with has_more, there are values left to fetch.

The same app lives on the other side of the fence, since Notion also has an n8n node. The choice comes down to your team and where the automation should run, not to a ranking. The n8n vs Make comparison sets out the criteria, the Notion n8n integration page covers the same ground for that tool, and Make training is there if you would rather be walked through the first builds.

Connect

How do you connect Notion to Make?

  1. 01

    Check your rights on the workspace

    You need a Notion account, and it has to carry admin permissions on the workspace, otherwise Make cannot set the link up at all. Nothing to install on the Notion side yet: the whole thing starts from a module inside a scenario.

  2. 02

    Create the connection from a module

    Drop any Notion module into a scenario and click Create a connection. In the Connection type dropdown, pick Notion Public to sign in as yourself, or Notion Internal to paste an internal integration token.

  3. 03

    Pick the pages Make can reach

    With Notion Public, Notion asks you to authenticate, then shows Select pages. Tick the pages and databases you want automated, click Allow access, then Save in Make. The modules will only ever see that selection.

First scenario

Your first scenario: a brief page for every new item

GoalWhen a new item lands in a Notion data source, Make creates the page that goes with it.

  1. 01

    Create the scenario

    From the Scenarios page in Make, create a new scenario and click the + to drop in the first module. Type Notion in the search and the full list of its modules comes up.

  2. 02

    Add the trigger

    Pick Watch Data Source Items as the first module, click Create a connection if you have not done it yet, then choose the data source you want watched.

  3. 03

    Add the action

    Click the + on the right of the trigger and add Create a Page. Map what the trigger sends into the fields of the action, so each new item writes its own page under the parent you choose.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles, the items travelling from one module to the next, so you can read what Notion really sent.

  5. 05

    Schedule it, then switch it on

    Set the clock on the first module. A new scenario runs every 15 minutes by default, which is also the floor on the free plan. Flip the switch and it keeps going without you.

Triggers

What can start a Notion scenario?

4 modules start a scenario when something happens in Notion. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Notion as soon as it happens.

Notion1Watch Data Source Items

Watch Data Source Items

Scheduled trigger

In Make“Triggers when a Data source (legacy database) item is created or updated.”

This one keeps an eye on a single data source and hands you every item created or updated in it, one bundle at a time.

How it fires
scheduled, meaning Make asks Notion what changed on the scenario's schedule instead of being told.
When to use it
a request table where each new row has to become a ticket, a folder or a message somewhere else.
Watch out
an update counts as a change too, so an item corrected twice comes back twice unless something filters downstream.
Notion2Watch Objects

Watch Objects

Scheduled trigger

In Make“Triggers when a data source, page or legacy database is created and updated.”

Watch Objects casts a wider net than the item trigger: it reports a data source, a page or a legacy database as soon as one is created or updated inside what your connection can reach.

How it fires
scheduled, so Make goes back to check Notion at the interval set on the first module.
When to use it
you want to know when someone opens a new page in a shared space, to log it or announce it.
Watch out
a wide net is a talkative one, and it will never see beyond the pages granted to your connection.
Notion3Watch Page Contents

Watch Page Contents

Scheduled trigger

In Make“Triggers when a page content is created.”

Where the other two follow items and objects, this trigger sits inside a page and reports each piece of content added to it, block by block.

How it fires
scheduled, so a new block reaches your scenario at the next check, not the second it is typed.
When to use it
a meeting page where the team drops decisions as they go, and every line has to travel somewhere.
Watch out
it reports content that gets created, so reworking an existing block is not what this one is for.
Notion4Watch Events

Watch Events

Instant trigger

In Make“Triggers when a specified event is created.”

Watch Events does not wait. Notion speaks up as soon as the event you picked happens, which is what sets this trigger apart from the other three in the list.

How it fires
instant, through a webhook, the alert an app sends Make the moment something happens, so the scenario starts on its own.
When to use it
an approval that has to reach the team right away.
Watch out
events only arrive for pages tied to your connection, and changing that list means creating a new connection and selecting the pages again.
Modules

What can Make do inside Notion?

Notion gives you 28 modules in 6 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Data Source/Database Item

5 modules
Notion1

Create a Data Source Item

Action

In Make“Creates a new item in a data source.”

Adds one item to the data source you choose, filled with whatever the previous module sent.

When to use it
a bug reported through a form has to land in the triage table without anyone retyping it.
Watch out
the data source has to sit inside the pages your connection reaches, otherwise it never shows up in the list.
Notion2

Create a Database Item (Legacy)

Action

In Make“Creates a new item in a database.”

Creates an item in a legacy database, the older target Make still lists next to data sources.

When to use it
the table your team has run on for two years is a legacy database and nobody is migrating it this quarter.
Watch out
anything you build from scratch belongs in the data source version, or you end up maintaining two paths for one job.
Notion3

Append a Database Item Content

ActionIn the docs only

Writes content at the bottom of a database item that already exists, rather than creating another one.

When to use it
a customer reply that belongs under the right account item, so the thread stays in one place.
Watch out
Make lists this module without a description, so try it on a throwaway item and see where the content lands before it touches real data.
Notion4

Update a Data Source Item

Action

In Make“Updates an existing data source (or legacy database) item.”

Changes an item that already exists, in a data source or in a legacy database, instead of piling up duplicates.

When to use it
a deal moves to signed in your CRM and the matching row in Notion should say the same thing.
Watch out
it acts on one item you point at, so a search usually runs before it to find the right target.
Notion5

Get a Data Source Item

Action

In Make“Gets a specified data source (or legacy database) item.”

Pulls one item and hands its content to the rest of the scenario, without changing anything.

When to use it
a recap that needs the current state of a single record rather than the whole table.
Watch out
it returns the one item you point at, so run a search first when you do not already know which one you want.

Data Source/Database/Page

13 modules
Notion6

Search Objects

Search

In Make“Searches for objects of a page, database, or database item.”

Looks through pages, databases and database items, and returns what matches as zero, one or several bundles.

When to use it
finding the account page that goes with an incoming email before writing anything into it.
Watch out
a search can come back empty, and the modules after it then run on nothing, so plan for that branch.
Notion7

Create a Database

Action

In Make“Creates a new database with default data source.”

Builds a new database, with its default data source, from inside a scenario.

When to use it
every new client gets the same tracking table, and generating it beats duplicating a template by hand.
Watch out
creating structure is rarely a daily job, so keep this one in a setup scenario you run on demand.
Notion8

Update a Database

Action

In Make“Updates an existing database.”

Edits the container itself, the database, not the rows sitting inside it.

When to use it
a title that has to follow the client's name, or a description nobody kept current.
Watch out
touching the container can ripple through the views and links your team relies on, so try it on a copy first.
Notion9

Get a Database

Action

In Make“Gets a specified database.”

Fetches the details of one database so the scenario can read them before deciding anything.

When to use it
a routing step that has to know which table it is dealing with before it writes a single line.
Watch out
reading the database is not reading its items, and that part belongs to Search Objects or to the item modules.
Notion10

Create a Data Source

Action

In Make“Adds a new data source to database or page.”

Attaches a new data source to a database or a page that already exists.

When to use it
an onboarding chain that gives each new project its own table, right inside the project page.
Watch out
the parent has to be reachable through your connection, so share it with the integration before the scenario runs.
Notion11

Update a Data Source

Action

In Make“Updates a data source.”

Applies a change to a data source that is already in place.

When to use it
renaming the table a scenario created, once the client name is confirmed and the placeholder has to go.
Watch out
it works on the data source, never on what it contains, so nothing here touches your items.
Notion12

Get a Data Source

Action

In Make“Gets a specified data source.”

A read and nothing more: it returns what one data source is.

When to use it
a check at the start of a run, to confirm the table you are about to write into is the one you think.
Watch out
it describes the container, so pair it with a search or an item module when you need the contents.
Notion13

Get a Page

Action

In Make“Gets a specified page.”

Opens one page and hands its properties to the rest of the scenario.

When to use it
a client recap that needs the status written on the project page before it goes out.
Watch out
properties are not the body, so use List Page Contents for the blocks written inside the page.
Notion14

Create a Page

Action

In Make“Creates a new page in a specified page.”

Your scenario can write documents, not only rows: this one creates a page inside a page you choose.

When to use it
every signed deal gets its own space, created under the client hub with the name already filled in.
Watch out
it needs a parent page your connection can see, which is the usual reason the list looks short.
Notion15

Update a Page

Action

In Make“Updates an existing page.”

Rewrites the properties of a page that already exists.

When to use it
a status that should flip on its own once the work is finished in another tool.
Watch out
it updates the page itself, while adding a paragraph to it is the job of Append a Page Content.
Notion16

Create a Database (Legacy)

Action

In Make“Creates a new database as a subpage in a specified page.”

The legacy twin of Create a Database: it drops a new database as a subpage of the page you name.

When to use it
a workspace still running on legacy databases that needs new ones matching the old shape.
Watch out
mixing both models in one workspace makes later scenarios harder to follow, so pick a side and write it down.
Notion17

Get a Database (Legacy)

Action

In Make“Gets a specified database.”

On the legacy side, this module reports what a given database is.

When to use it
an inventory pass across the old tables, to see which ones are still in use before anyone cleans up.
Watch out
if the table was built recently, check whether it is a data source, because each model has its own modules here.
Notion18

Update a Data Source (Legacy)

ActionIn the docs only

Make lists this one in its documentation without a description, which tells you how narrow the case is: it updates a data source on the legacy side.

When to use it
a cleanup pass on an old workspace, where the legacy shape is simply what you have.
Watch out
no description means no promises, so run it on one table, read what comes back, then wire it into anything that matters.

Page Content

6 modules

Add the List Page Property Items module to retrieve the complete details of a property item if the output variable contains the has_more value. This means you must paginate to retrieve all the property item's property values in the page object as Notion imposes a 25-page reference limit.

In the Type field, select the page content type that corresponds to the Page Content ID. If an incorrect Type is selected, an error will appear. The page content type cannot be changed using this module.

Notion19

List Page Contents

Search

In Make“Retrieves a list of page contents.”

Hands back the blocks of a page, in order, as a series of bundles.

When to use it
turning a meeting page into an email, or checking that a template page still has every section.
Watch out
a long page produces a long list, and the modules after it run once per block, so filter before you act.
Notion20

List Page Property Items

Search

In Make“Retrieves a list of paginated page property items. Possible property types are title, text, relation, and person.”

Pages through the values of a single property, which is what you need for title, text, relation and person properties.

When to use it
a page whose relation property points at more entries than the page object carries.
Watch out
Notion stops at 25 references in a page object, and a module answering with has_more is telling you to come here for the rest.
Notion21

Get a Page Content

Action

In Make“Get a specified page content/block.”

Grabs a single block and returns it as it stands.

When to use it
reading one specific paragraph before the scenario decides whether it needs rewriting.
Watch out
one block is all you get, so reach for List Page Contents when the whole page matters.
Notion22

Append a Page Content

Action

In Make“Appends a new page content.”

Appends new content at the end of a page, under what is already written.

When to use it
a log page that collects what happened, one line per run instead of a new page every time.
Watch out
it appends and never replaces, so a scenario that runs twice on the same input writes twice.
Notion23

Update a Page Content

Action

In Make“Updates an existing page content/block.”

Edits a block that is already on a page.

When to use it
a status line at the top of a page that should always show the latest figure.
Watch out
the Type you select has to match the content behind the Page Content ID, or an error appears, and the type of a block cannot be changed here.
Notion24

Delete a Page Content

Action

In Make“Sets a page content/block, as archived.”

Archives a block, which is how content leaves a Notion page.

When to use it
clearing the placeholder section once an earlier module has written the real content.
Watch out
there is no undo inside a scenario, so put a filter in front of it and test with Run once before switching anything on.

Users

1 module
Notion25

List Users

Search

In Make“Retrieves a list of users.”

Returns the people in the workspace your connection reaches.

When to use it
matching a name coming from another app with the right person before anything gets assigned.
Watch out
it reads and never writes, and it knows only the workspace behind your connection.

Other

1 module
Notion26

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends your own request to the Notion API, the technical door of the app, using the connection you already created. It covers whatever the 32 listed modules do not.

When to use it
an endpoint no module here exposes, once you have read the Notion API documentation.
Watch out
nothing is prepared for you, so expect to shape the request yourself and test it with Run once before it matters.

Other modules

2 modules
Notion27

Append a Data Source Item Content

Action

In Make“Appends a new data source item content.”

Drops content inside an item of a data source, after what is already there.

When to use it
a candidate record that collects interview notes as they come, with no extra page per round.
Watch out
the item has to exist first, so a create or a search usually comes earlier in the flow.
Notion28

Update a Database (Legacy)

Action

In Make“Updates an existing database.”

Closes the legacy set: it updates a legacy database that already exists.

When to use it
retitling an old table a scenario keeps writing into, without opening Notion to do it by hand.
Watch out
several modules here target legacy objects, and keeping them straight is easier if your scenarios are named accordingly.
Need help

Need help automating Notion with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Notion Make integration free?
Yes, on the free plan. Notion is a standard app in Make, so it comes with every plan and there is no add-on to buy. What the free plan limits is the running, not the app: two active scenarios, a floor of 15 minutes between two scheduled runs, five minutes of execution per run, files up to 5 MB and 512 MB of transfer. Each module that processes one item counts as one operation, the unit Make bills against your plan, so a chain that touches many items costs more than one that touches a few. Paid plans bring the interval down to one minute and lift the cap on active scenarios.
02What do you need to connect Notion to Make?
A Notion account holding admin permissions on the workspace, and nothing else. You add a Notion module to a scenario, click Create a connection, then choose between Notion Public, where you sign in and pick the pages Make may reach, and Notion Internal, where you paste an internal integration token generated from Settings and Members, then Connections, then the integrations page. The public route also asks you to click Select pages and Allow access. Either way, Make sees only the pages you granted, which is worth deciding before you start rather than after.
03Does Notion trigger Make in real time?
It depends on the trigger. Three of the four are scheduled: Watch Data Source Items, Watch Objects and Watch Page Contents ask Notion what changed each time the scenario runs, which is every 15 minutes by default and no faster than that on the free plan. Watch Events is the instant one, since Notion calls Make through a webhook as soon as the event happens and the scenario starts by itself. If minutes matter, build on Watch Events. If you are batching work, a scheduled trigger is steadier and easier to reason about.
04What if a module is missing or a limit gets in the way?
Make an API Call answers the missing module: it sends your own request to the Notion API through the connection you already created, so any endpoint the API exposes is reachable from a scenario. Two limits are worth knowing before you design around them. Notion stops at 25 property references in a page object, and List Page Property Items exists to page through the rest when a module answers with has_more. Events reach only the pages tied to your connection, so widening the scope means creating a new connection and selecting the pages again.
05Make or n8n for Notion?
Both cover the app, so it depends on your team. Make puts everything on a canvas: you drag modules, map fields by clicking, and the 32 Notion modules listed above are ready as they are. n8n asks more of you and gives more room to people comfortable with code. If nobody on the team wants to open a code editor, Make is the safer pick for this app, and the first scenario above is a fair picture of the effort involved. If your workspace is one piece of a larger technical setup, read the comparison linked earlier before you commit either way.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations