Resources · Make integration

Boost Note Make integrationAutomate Boost Note with Make.

Can Make keep your Boost Note docs and folders in order without code? Yes. The Boost Note Make integration gives you 10 modules, 8 actions and 2 searches, to create, read, update and delete documents and folders. This page walks you through the connection and a first scenario.

Try the Boost Note integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Boost Note Make integration do for your team?

The Boost Note Make integration links your Boost Note account to Make, so a scenario (the automation you build in Make) can create, read, update or delete documents and folders for you. Each step of a scenario is a module, and Boost Note brings ten of them.

A ready workspace for every new client. When a deal closes in your CRM, Create a Folder opens a space named after the client and Create a Document drops a kickoff note inside it. Nobody has to remember the setup.

Docs that follow the source. When a spec changes in your project tool, Update a Document rewrites the matching Boost Note page, so engineers read the current version instead of a stale copy.

An inventory you can reuse. List Documents and List Folders return what sits in your workspace, one bundle (one item passed to the next module) per result. Send that list to a spreadsheet or a reporting tool.

Boost Note has no trigger in Make, so it never starts a scenario by itself: the start comes from another app or from a schedule. When the ten modules fall short, Make an API Call reaches the rest of the API. New to the editor? The Make training covers the basics, Make pricing explains how usage is counted, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect Boost Note to Make?

  1. 01

    Generate a token in Boost Note

    In Boost Note, open Settings, then Integrations, and go to the Access Tokens section. Click Generate Token and copy the API key shown on screen. This needs an active Boost Note account.

  2. 02

    Add a Boost Note module in Make

    Log in to Make, add any Boost Note module to your scenario and click Create a connection. A connection is your Boost Note account linked to Make once, then reused by all ten modules.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps if you run several workspaces. Paste the API key, or follow the on-screen instructions, and save. Make can now read your folders and documents.

First scenario

Your first scenario: a Boost Note folder and doc for each new client

GoalWhen a new client lands in your CRM, Make creates a Boost Note folder and a first document inside it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that holds your new clients, such as your CRM, and choose its trigger.

  2. 02

    Add Create a Folder

    Click the + on the right of that first module, search for Boost Note and pick Create a Folder. Select your connection, then map data from the previous module, like the client name.

  3. 03

    Add Create a Document

    Add one more module: Boost Note, Create a Document. Map data from the two modules before it so the page lands in the new folder, with the details the team should read first.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Open Boost Note and check that the folder and its document are there.

  5. 05

    Schedule and switch on

    Set the schedule on the first module: every 15 minutes by default, and never below 15 on the Free plan. Then switch the scenario on, and each new client gets a workspace.

Modules

What each Boost Note module does

Boost Note gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Boost Note1

Create a Document

ActionIn the docs only

Create a Document adds a new page to your Boost Note workspace from data your scenario already holds, such as a form answer or a closed deal. Each run costs one operation, meaning one execution of one module that Make counts on your plan.

When to use it
a meeting note, a brief or a checklist should exist the moment its event happens in another tool.
Watch out
it runs once per bundle it receives, so a search placed before it can multiply the new pages.
Boost Note2

Create a Folder

ActionIn the docs only

Structure first: Create a Folder gives a client or a project its own place in Boost Note, so the documents your scenario writes later have somewhere to land.

When to use it
a new account, product or event starts and you want the same folder layout every single time.
Watch out
to avoid two folders for the same client, look it up with List Folders before this module runs.
Boost Note3

Delete a Document

ActionIn the docs only

Delete a Document removes one page from Boost Note, which keeps the workspace free of drafts nobody opens anymore. Treat every deletion as permanent.

When to use it
a record is closed or cancelled in another tool and its Boost Note page should go with it.
Watch out
try it with Run once on a throwaway document before you point it at real content your team still reads.
Boost Note4

Delete a Folder

ActionIn the docs only

Clean-up at folder level: Delete a Folder takes a whole Boost Note folder out of the workspace when a project ends, instead of one page at a time.

When to use it
a client leaves or a project gets archived in your main tool, and the workspace should reflect it.
Watch out
confirm with Get a Folder that you are aiming at the right one, and test on a dummy folder with Run once.
Boost Note5

Get a Document

ActionIn the docs only

Get a Document reads one specific Boost Note page and hands its data to the next module, where you can reuse it in an email, a ticket or a chat message.

When to use it
you already know which document you need, often because an earlier module returned it.
Watch out
it returns a single item; to browse several pages at once, start with List Documents instead.
Boost Note6

Get a Folder

ActionIn the docs only

When a scenario needs the details of one folder, Get a Folder fetches them so the following modules can work with that folder's data.

When to use it
right before Create a Document or Delete a Folder, to confirm you are aiming at the right place.
Watch out
like its document twin, it targets one folder per run; List Folders is the module for a wider look.
Boost Note7

List Documents

SearchIn the docs only

List Documents is a search: it returns zero, one or several documents, each as its own bundle, so the next modules run once per document found.

When to use it
building an index of your pages in a spreadsheet, or updating a batch of documents in one pass.
Watch out
every bundle that goes through a later module counts as one more operation, so a long list weighs on your plan.
Boost Note8

List Folders

SearchIn the docs only

To see how your workspace is laid out, List Folders returns each folder as a separate bundle, or nothing at all when there is no match.

When to use it
checking whether a client already has a folder before Create a Folder runs, or copying the structure into another tool.
Watch out
plan for the empty case; when no folder comes back, the modules after it have nothing to work on.
Boost Note9

Make an API Call

ActionIn the docs only

Make an API Call is the way out when the other nine modules do not cover your need: it calls any endpoint of the Boost Note API with the same connection.

When to use it
a Boost Note feature you rely on has no dedicated module in this list.
Watch out
you build the request yourself, which takes more care than a ready module, so read the bundle it returns after a Run once.
Boost Note10

Update a Document

ActionIn the docs only

Update a Document changes an existing Boost Note page instead of creating a new one, so the team keeps a single page rather than a pile of copies.

When to use it
the source of a document changes in another app, for example a spec edited in your project tool.
Watch out
it needs to know which page to change; find it first with List Documents or Get a Document.
Need help

Need help automating Boost Note with Make?

A person reads every message.

FAQ

Boost Note and Make: common questions

01Is the Boost Note Make integration free?
Yes. Boost Note is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month. You also need an active Boost Note account, and its subscription is priced by Boost Note.
02What do you need to connect Boost Note to Make?
An active Boost Note account and an API key. In Boost Note, go to Settings, then Integrations, open the Access Tokens section and click Generate Token. Copy the key, add a Boost Note module in Make, click Create a connection and paste it in. The Connection name field is optional. Once saved, that single connection serves all ten Boost Note modules, so you set it up only once per account. If you manage more than one workspace, give each connection a name you will recognize later.
03Can Boost Note start a Make scenario on its own?
No. Boost Note has no trigger module in Make, so nothing in Boost Note can launch a scenario. You start it another way. Either another app's trigger opens the flow, for example a new deal or a form entry, and Boost Note modules follow. Or you put a Boost Note search such as List Documents first and let Make's schedule run it: every 15 minutes by default, 15 minutes minimum on the Free plan and 1 minute on paid plans. In both cases, the timing depends on the first module, not on Boost Note.
04What if a Boost Note module is missing in Make?
Use Make an API Call. It calls any endpoint of the Boost Note API through the connection you already have, so you can reach features the eight actions and two searches do not cover. You write the request yourself, which takes more care than filling a ready module, so test it with Run once and read the bundle it returns before switching the scenario on. The Make documentation for this app lists no specific limits, and it warns that its content is generated from Boost Note's own docs, so check anything critical with Boost Note.
05Make or n8n for Boost Note?
It depends on what your team already runs. On Make, Boost Note comes with 10 ready modules, 8 actions and 2 searches, plus Make an API Call, all sharing one connection. Check first whether n8n has a dedicated Boost Note node, since that changes how much you build by hand. The criteria that matter are the same on both sides: which other apps the workflow touches, who on the team will maintain it, and how usage is counted on each plan. The comparison page linked earlier goes through those points one by one.
Same platform

Other docs you might need on this stack.

Browse all integrations