Resources · Make integration

Roam-bot Make integrationAutomate Roam-bot with Make.

Get notes from your other tools into Roam-bot without copy and paste. The Roam-bot Make integration offers 10 modules: 3 triggers, 6 actions and 1 search. This page shows how to link your account, then walks you through a first scenario, step by step.

Try the Roam-bot integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Roam-bot Make integration do for you?

The Roam-bot Make integration lets Make read and write your Roam-bot graph for you. It spots new blocks, new pages and edited pages, and it adds blocks where you want them, whether that is today's page, the Quick Capture page or a page you pick, all without writing a line of code.

An inbox that fills itself. Point a form, an email tool or a chat app at Create a Block in Quick Capture Page, and every entry lands as a block you can sort later. Nothing gets lost between tools.

A daily log written for you. With Create a Block in Today Page, events from other apps (a closed deal, a new ticket, a meeting booked) show up on the page of the day, so your journal reflects what actually happened.

Pages that talk to the rest of your stack. Watch New Page and Watch Updated Page let a new or edited page start work elsewhere, such as a task in your project tool or a message to a teammate. When you need a precise target, Search a Page by its Title finds it first.

Know the limit before you start: Make itself says its documentation for Roam-bot is limited, because little public information exists about the app. Expect to test each module with Run once. If you are weighing tools, read our n8n vs Make comparison; to learn the editor properly, see the Make training; and if a run fails, start with Make troubleshooting.

Connect

How do you connect Roam-bot to Make?

  1. 01

    Add a Roam-bot module

    In your scenario, click the + and search for Roam-bot. Pick any of its modules, then click Create a connection. A connection is your Roam-bot account linked to Make once, then reused by every Roam-bot module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when you manage several graphs. Then authorize Make on the Roam-bot page that opens, or paste the key Roam-bot gives you, depending on what the connection window asks for.

  3. 03

    Save and check the lists

    Click Save. Once the connection exists, Make can read what your account allows and fill the module fields with it, so a working connection shows up right away in the options you get.

First scenario

Your first scenario with Roam-bot and Make

GoalWhen a new entry arrives in another app, Make writes it as a block in your Roam-bot Quick Capture page.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add its first module. A scenario is the automation you build: a chain of modules that runs on a schedule or when an app calls Make.

  2. 02

    Choose where entries come from

    Add the trigger of the app where your notes start, for example a form tool or your email app, and create its connection. This first module decides what sets the whole scenario in motion.

  3. 03

    Add the Roam-bot block

    Click the + on the right of the first module, search for Roam-bot and pick Create a Block in Quick Capture Page. Create your Roam-bot connection, then map the text from the previous module into the block.

  4. 04

    Test with Run once

    Click Run once, then send a test entry in the first app. Make runs the scenario one time and shows the bundles each module received, so you can check that the block text looks right in Roam-bot.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Then switch the scenario on, and new entries keep landing in Quick Capture without you touching them.

Triggers

What starts a Roam-bot scenario

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

Roam-bot1Watch New Block

Watch New Block

triggerIn the docs only

Catch fresh ideas once they become blocks, and send them where they can turn into work. This trigger returns each new block as a bundle, meaning one item passed to the next module, so you can copy it to a task list or alert a teammate.

How it fires
it is a scheduled trigger, so Make checks Roam-bot on the scenario's schedule rather than being called by the app.
When to use it
you jot quick notes in Roam-bot and want each one reviewed or shared somewhere else.
Watch out
every block counts, so if you write a lot, add a filter after this module to keep only the blocks that matter.
Roam-bot2Watch New Page

Watch New Page

triggerIn the docs only

Turn every new page into a follow-up in your other tools. When a page appears in your graph, this trigger passes it on as a bundle, ready to open a task, notify a channel or log the topic in a spreadsheet.

How it fires
scheduled; Make checks Roam-bot on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
each new page stands for a new client, project or meeting that someone else needs to hear about.
Watch out
a page is new only once; if your team adds details later, pair it with Watch Updated Page instead.
Roam-bot3Watch Updated Page

Watch Updated Page

triggerIn the docs only

Keep other tools in step with pages that change. This trigger hands Make each page that was edited, so a status note, a revised brief or a meeting summary can travel on to the people who rely on it.

How it fires
scheduled; Make looks at Roam-bot on the scenario's schedule, not the second a change is typed.
When to use it
a page acts as a living document, like a project brief, and edits must reach a task tool or a teammate.
Watch out
if the same scenario writes back to the page it watches, that write may itself look like an update, so test with Run once before you switch it on.
Modules

What Roam-bot can do in a scenario

Roam-bot gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Roam-bot1

Create a Block Under an Existing Block by Its Unique ID

ActionIn the docs only

Nest new content exactly where it belongs, as a child of a block you already have. You point Make at the parent through its unique ID, so the new block sits under the right heading instead of floating at the bottom of a page.

When to use it
a meeting block collects follow-ups, and each new action item should appear indented under it.
Watch out
you need the parent's unique ID first, mapped from a previous module.
Roam-bot2

Create a Block in Quick Capture Page

ActionIn the docs only

Give yourself one inbox inside Roam-bot. This action drops a block into the Quick Capture page, so anything collected by another tool waits in a single spot until you sort it.

When to use it
ideas arrive from forms, emails or chat and you have no clear page for them yet.
Watch out
Quick Capture fills up fast if every event lands there; add a filter before this module when the source is noisy.
Roam-bot3

Create a Block in Today Page

ActionIn the docs only

Build a journal that writes itself. The action adds a block to the page of the current day, so what happens in your other apps sits next to your own notes for that date.

When to use it
you want a running log of sales, tickets or bookings on the day they occur, without typing it.
Watch out
the block always goes to today's page; to file something under an older date, use a specific page module instead.
Roam-bot4

Create a Block in a Specific Page

ActionIn the docs only

Send content straight to the page you name, such as a client file or a reading list. You choose the page once in the module, and every run adds its block there, which keeps related notes together.

When to use it
one page gathers everything about a topic, for instance all feedback on a product.
Watch out
if the page title changes later, check the module still targets the right page, or switch to the unique ID version.
Roam-bot5

Create a Block in a Specific Page by Its Unique ID

ActionIn the docs only

Write to a page without depending on its title. Because the page is identified by its unique ID, the scenario keeps finding it even after someone renames it, which suits pages that change name as a project moves on.

When to use it
the page ID comes from Search a Page by its Title or from a trigger, and you want a stable target.
Watch out
map the ID from a previous module rather than typing it by hand, to avoid a silent typo.
Roam-bot6

Make an API Call

ActionIn the docs only

Reach the parts of Roam-bot that the listed modules leave out. This module calls any endpoint of the Roam-bot API from your scenario, reusing the same connection, so you do not set up a second login.

When to use it
you need something none of the other nine modules covers, and you know which endpoint handles it.
Watch out
Make says its Roam-bot documentation is limited, so check the endpoint on the Roam-bot side and test with Run once.
Roam-bot7

Search a Page by its Title

SearchIn the docs only

Find the page a scenario should work on before it writes anything. You give a title, and the search returns what matches, ready for the next module to use; check with Run once whether the result carries the page's unique ID.

When to use it
the page name arrives from another app, say a client name from your CRM, and you need to locate that page first.
Watch out
a search can return zero, one or several bundles, so plan for the case where nothing matches.
Need help

Need help automating Roam-bot with Make?

A person reads every message.

FAQ

Roam-bot and Make: common questions

01Is the Roam-bot Make integration free?
Yes, Roam-bot is a standard app, so it works on the Make Free plan. The Free plan has limits: 2 active scenarios, at least 15 minutes between two 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, allow unlimited active scenarios and 40 minutes of execution. Make counts usage in operations, one module running on one bundle, so a busy Roam-bot scenario uses more of your monthly credits.
02What does it take to connect Roam-bot to Make?
A Roam-bot account and a Make account. The Make documentation lists no prerequisite for this app and gives no dedicated connection steps, so the standard flow applies: add any Roam-bot module, click Create a connection, optionally name it, authorize Make on the Roam-bot page or paste the key Roam-bot provides, then click Save. The connection is created once and every Roam-bot module in your scenarios reuses it. Since the documentation is limited, test the first module with Run once to confirm the link works.
03Do Roam-bot triggers start a Make scenario instantly?
No. All 3 Roam-bot triggers, Watch New Block, Watch New Page and Watch Updated Page, are scheduled (Make's doc only lists them, so this type is read from their Watch names). Make checks Roam-bot on the scenario's schedule instead of waiting for the app to call it. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans can go down to 1 minute. If you need a faster reaction, shorten the schedule on the first module within what your plan allows.
04What if a Roam-bot module is missing in Make?
Use Make an API Call. It is part of the Roam-bot app in Make and calls any endpoint of the Roam-bot API with the connection you already have, so you are not limited to the 9 other modules. Make itself warns that its Roam-bot documentation is limited because little public information exists about the app, so check the endpoint on the Roam-bot side before building on it. Test each call with Run once and read the returned bundle to see exactly what comes back.
05Make or n8n for Roam-bot: which one fits?
It depends on where Roam-bot is covered for your use case. In Make, Roam-bot offers 10 modules: 3 scheduled triggers, 6 actions including Make an API Call, and 1 search, available from the Free plan. The same app often has an n8n node too, but this page only documents the Make side, so check the n8n node list before deciding. Compare the modules each tool gives for the exact job you have in mind, such as writing to the daily page, and pick the one that covers it without workarounds.
Same platform

Other docs you might need on this stack.

Browse all integrations