Resources · Make integration

Boost.space Make integrationAutomate Boost.space with Make.

Your Boost.space records can move on their own once Make watches them. The Boost.space Make integration offers 33 modules: 9 triggers, 20 actions and 4 searches. This guide connects your account, builds a first scenario with you and explains each module in plain words.

Try the Boost.space integration on MakeSee the 33 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Boost.space Make integration do for you?

The Boost.space Make integration links your Boost.space account to Make, so records, fields, modules and spaces can be created, read, changed or removed by a scenario, which is the automation you build in Make. Each scenario is a chain of modules, and every module is one brick: a trigger, an action or a search.

Keep other tools aligned with Boost.space. Watch updated records spots edited records, and the next module pushes the change to your CRM or your mailing tool. One edit in Boost.space, and the other side follows.

Feed Boost.space from the tools your team already uses. A form, a shop or a spreadsheet can start the scenario, then Create a record or Bulk create records (advanced) writes the data where everyone can see it.

Watch the structure, not only the data. Watch created modules and Watch deleted modules tell you when someone reshapes the setup, which is useful for the person in charge of keeping things tidy.

Be clear about the limits. All 9 triggers are scheduled, so Make checks for changes on a timer rather than hearing about them instantly. Make's documentation for this app also warns that its content is AI-generated and may contain mistakes, so test each module with Run once before relying on it. When a listed module falls short, Make an API Call reaches the rest of the Boost.space API with the same connection.

New to Make? Read our Make review first, or follow the Make training. Boost.space may also exist on the n8n side, and n8n vs Make lays out how the two tools differ.

Connect

How do you connect Boost.space to Make?

  1. 01

    Gather your two keys in Boost.space

    You need an active Boost.space account. Copy your system key: it is the part of your Boost.space address that sits before .boost.space. Then open your profile, go to API tokens, create a token, pick its privileges and copy it.

  2. 02

    Add a Boost.space module in Make

    In your scenario, click the + and search for Boost.space. Pick any module, then click Create a connection. A connection is your Boost.space account linked to Make once and reused by every Boost.space module afterwards.

  3. 03

    Paste the credentials and save

    Give the connection a clear label in Connection name if you manage several accounts. It is optional. Paste the system key and the API token you copied, or follow the instructions Make shows on screen, then confirm.

First scenario

Your first scenario with Boost.space

GoalWhen an item changes in another app, Make finds the matching Boost.space record by its RemoteID and updates it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Here it comes from the other app you use, such as your shop or your CRM, and watches the items you care about.

  2. 02

    Find the Boost.space record

    Click the + on the right, search for Boost.space and pick Get a record by RemoteID. Click Create a connection if you have none yet, then map the identifier sent by the first module.

  3. 03

    Add the update

    Add Update a record after it. Map the record found in the previous step, then map the new values coming from the first app into the fields you want to refresh.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, a bundle being one item passed along the chain. Check that the right record changed in Boost.space.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan. Keep it or pick another interval, then switch the scenario on.

Triggers

Boost.space triggers in Make

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

Boost.space1Watch - Custom Module Item Created

Watch - Custom Module Item Created

triggerIn the docs only

Starts your scenario when a new item appears in one of your custom Boost.space modules, so each entry travels to the next step as its own bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so new items arrive in groups rather than the second they are saved.
When to use it
your team built a custom module for supplier requests, and each new request should land in your accounting tool.
Watch out
Make's documentation gives no description of this trigger, so add a test item, click Run once and read the bundle before you build further.
Boost.space2Watch created modules

Watch created modules

triggerIn the docs only

Reports every module newly added to your Boost.space setup, which helps when the structure matters as much as what goes into it.

How it fires
scheduled. Make checks the app on the scenario's schedule and passes along the modules created since its last look.
When to use it
an admin wants each new module logged in a shared sheet so nobody builds a duplicate by accident.
Watch out
Watch new module has a very close name and the documentation does not explain how they differ. Try both with Run once and keep the one whose output suits you.
Boost.space3Watch created records

Watch created records

triggerIn the docs only

Hands each record freshly created in Boost.space to your scenario, one bundle per record, so the rest of the chain can act on it.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a record created now shows up at the next check, not instantly.
When to use it
a lead typed into Boost.space by a sales rep should receive a welcome email from your mailing tool.
Watch out
Watch new records sounds almost identical. Nothing in the documentation separates them, so compare their bundles in a test run before you commit to one.
Boost.space4Watch deleted modules

Watch deleted modules

triggerIn the docs only

Tells your scenario that a module has disappeared from Boost.space, giving you a trace of structural changes that would otherwise go unnoticed.

How it fires
scheduled. Make checks the app on the scenario's schedule and reports the removals it finds at that moment.
When to use it
the operations lead wants a message in the team chat whenever someone removes a module.
Watch out
by the time the bundle reaches Make, the module is most likely gone, so a Get a custom module placed after it may find nothing. Work from the data the trigger itself carries.
Boost.space5Watch deleted records

Watch deleted records

triggerIn the docs only

Catches records removed from Boost.space, so the tools connected to it can be cleaned the same way and keep matching data.

How it fires
scheduled. Make checks the app on the scenario's schedule, which means a deletion is picked up at the next check.
When to use it
a contact deleted in Boost.space should also leave your newsletter list and your CRM.
Watch out
skip Delete a record on Boost.space in the same scenario. The record has most likely disappeared already when the bundle arrives, so that action would have nothing to remove.
Boost.space6Watch new module

Watch new module

triggerIn the docs only

Flags a module that did not exist at Make's previous check, a second route for spotting fresh structure in your Boost.space account.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns what is new since then.
When to use it
every new module should get a matching folder in your file storage, created without anyone thinking about it.
Watch out
it overlaps in name with Watch created modules. Run both once on the same test module, then keep a single one so the same module does not trigger two scenarios.
Boost.space7Watch new records

Watch new records

triggerIn the docs only

Picks up the records added to Boost.space since the last check and sends them down your scenario, ready to be copied, enriched or announced.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default and never faster than that on the Free plan.
When to use it
a new product record should appear in your online catalog without anyone copying it by hand.
Watch out
with Watch created records so close in name, pick one after a Run once comparison instead of guessing.
Boost.space8Watch updated modules

Watch updated modules

triggerIn the docs only

Notices a module whose settings changed in Boost.space and brings that change into your scenario, so structural edits never slip past you.

How it fires
scheduled. Make checks the app on the scenario's schedule and lists the modules changed since its previous pass.
When to use it
whoever documents your data setup wants a note each time a module is edited, pushed to a shared page.
Watch out
an Update a module later in the same scenario is likely to count as a new change at the next check and start the scenario again, a loop that eats operations.
Boost.space9Watch updated records

Watch updated records

triggerIn the docs only

Sends every edited record to your scenario, the trigger to pick when a change in Boost.space must reach your other tools.

How it fires
scheduled. Make checks the app on the scenario's schedule, so an edit made now travels at the next check.
When to use it
a customer status changed in Boost.space should update the same customer in your CRM.
Watch out
ending that scenario with Update a record on the same records is likely to create a fresh edit each run, which the next check would pick up again. That loop burns operations, where an operation is one module run counted on your plan.
Modules

What each Boost.space module does in Make

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

Boost.space1

Bulk create records (advanced)

ActionIn the docs only

Writes many records in one module instead of one run per record, which keeps the scenario short when a whole list shows up together.

When to use it
you import a batch of rows from a spreadsheet, such as a product list shared by a supplier.
Watch out
the documentation says nothing more about its settings, so start with a small list and a Run once test.
Boost.space2

Create a custom module

ActionIn the docs only

Builds a brand new custom module in Boost.space from the scenario, giving a home to a kind of data you did not track yet.

When to use it
each signed client project needs its own register, set up the moment the deal closes in your CRM.
Watch out
behind a trigger that fires often, it creates one module per bundle. Place it where it runs only when truly needed.
Boost.space3

Create a field

ActionIn the docs only

Adds a field to an existing module, so a new piece of information has a place to live before records start filling it.

When to use it
a form in another tool gains a question and Boost.space has to keep the answer.
Watch out
put this step before any Create a record that writes into the new field, otherwise the value has nowhere to go.
Boost.space4

Create a record

ActionIn the docs only

Saves one new record in a Boost.space module with the values you map from earlier modules. It is often the last step of a scenario that feeds Boost.space.

When to use it
each new order in your shop should become a record your team can follow.
Watch out
if the source may send the same item twice, look it up first with Get a record by RemoteID to avoid duplicates.
Boost.space5

Create a space

ActionIn the docs only

Opens a new space in your Boost.space account from Make, ready to receive the modules you add next.

When to use it
a new team or a new client account should get its own space as soon as it is registered elsewhere.
Watch out
the documentation does not say a new space comes with any module inside. Follow it with Create a custom module if structure is needed right away.
Boost.space6

Delete a field

ActionIn the docs only

Removes a field from a module once it serves no one, which keeps the module easier to read for the people using it.

When to use it
a migration is finished and the temporary field used during it can go.
Watch out
the documentation mentions no way to undo a deletion. Test the scenario on a copy module first, and treat every run as final.
Boost.space7

Delete a module

ActionIn the docs only

Deletes a whole Boost.space module, the most drastic action in this list after Delete a space.

When to use it
temporary modules created for a one-off project should disappear once that project is closed in your project tool.
Watch out
the documentation mentions no way to restore it afterwards. Feed it only module identifiers you checked with List modules, never a value typed by hand.
Boost.space8

Delete a record

ActionIn the docs only

Removes a single record from Boost.space, so data that should no longer exist stops showing up for your team.

When to use it
a customer asks to be forgotten in your support tool and the matching record must go too.
Watch out
treat the deletion as final, since the documentation mentions no way back. Take the record identifier from Get a record or List records rather than typing it.
Boost.space9

Delete a space

ActionIn the docs only

Deletes an entire space, the widest cleanup available among the Boost.space modules in Make.

When to use it
a client relationship ends and the space opened for it has to be closed in the same move as the rest of the offboarding.
Watch out
the documentation mentions no undo, so treat it as final. Run it only on a space found with List spaces or Get a space, and test on a dummy space first.
Boost.space10

Get a custom module

ActionIn the docs only

Reads the details of one custom module so later modules can reuse them in their mapping, for instance its name in a message.

When to use it
a trigger gives you only a module identifier and your notification needs something a human can read.
Watch out
it reads one module you already know. To browse several, List modules is the better pick.
Boost.space11

Get a field

ActionIn the docs only

Fetches the definition of one field, useful when a later step has to know what a field is before writing into it.

When to use it
a scenario checks that a field still exists before Update a field renames it.
Watch out
it returns one field. For the full structure of a module in a single pass, List fields schema fits better.
Boost.space12

Get a record

ActionIn the docs only

Pulls the full content of one record when you already know which one you need, so the next module has every value at hand.

When to use it
another app passes only a record identifier and your invoice step needs the rest of the details.
Watch out
without a known identifier, reach for List records, which can search and return several records.
Boost.space13

Get a record by RemoteID

ActionIn the docs only

Finds a record through its RemoteID instead of the Boost.space identifier, the natural bridge when you only hold the reference used by another tool.

When to use it
an order changes in your shop and you need the matching Boost.space record before updating it.
Watch out
the documentation does not explain how the RemoteID gets filled. Open a record in a Run once output to confirm it is there.
Boost.space14

Get a space

ActionIn the docs only

Returns the details of one space so you can print its name in a message or pass it to the next module.

When to use it
a report sent to a manager should say which space a change happened in, in words rather than an identifier.
Watch out
it reads a single space you already identified. List spaces is the one to browse them all.
Boost.space15

List fields schema

SearchIn the docs only

Lays out the fields of a module as bundles, a quick way to understand a structure before mapping data into it.

When to use it
you document your Boost.space setup and want every field of a module copied into a shared sheet.
Watch out
as a search, it can return zero, one or many bundles, and each bundle sent onward runs the following modules again.
Boost.space16

List modules

SearchIn the docs only

Returns the modules of your Boost.space account, the starting point for any audit or cleanup of the structure.

When to use it
before a reorganization, you want an inventory of every module in a spreadsheet.
Watch out
each module found becomes its own bundle, so a Delete a module placed right after would act on all of them. Check the list first.
Boost.space17

List records

SearchIn the docs only

Searches the records of a module and sends back every match, the tool for checking whether something already exists before you create it.

When to use it
a new sign-up arrives from your website and you want to know if that person is already in Boost.space.
Watch out
an empty result still counts as a result. Plan what the scenario does when zero bundles come out.
Boost.space18

List spaces

SearchIn the docs only

Gives you the spaces available in your account, each one as a bundle, so a scenario can pick the right space without a hardcoded value.

When to use it
a summary per team needs to cover every space, one pass each.
Watch out
the next modules run once per space found, which multiplies operations on a large account.
Boost.space19

Make an API Call

ActionIn the docs only

Calls any endpoint of the Boost.space API from your scenario, reusing the same connection, for the cases the listed modules do not cover.

When to use it
you need an operation from the Boost.space API that none of the other listed modules offers.
Watch out
you write the request yourself, so keep the Boost.space API reference open and test the call with Run once.
Boost.space20

Sync a record

ActionIn the docs only

As its name says, it keeps a Boost.space record in step with the data your scenario sends, a middle ground between creating and updating.

When to use it
you receive items from another tool without knowing whether they already exist in Boost.space.
Watch out
Make's documentation gives no description of this module. Check its behavior on test data with Run once before trusting it with real records.
Boost.space21

Update a field

ActionIn the docs only

Changes an existing field in a module, for example to give it a clearer label, without touching the records around it.

When to use it
your team renames a concept, and the field has to follow in Boost.space as it does in your other tools.
Watch out
other scenarios mapping that field may need a check afterwards. Run them once to confirm they still behave.
Boost.space22

Update a module

ActionIn the docs only

Edits the settings of an existing module from Make, handy when the same structural change has to reach several modules.

When to use it
a new naming convention is adopted and every module listed by List modules must follow it.
Watch out
a scenario that starts with Watch updated modules and ends here can restart itself on each check. Keep them apart.
Boost.space23

Update a record

ActionIn the docs only

Writes new values into a record that already exists, so Boost.space reflects what just changed elsewhere.

When to use it
a payment clears in your billing tool and the customer record needs its new status.
Watch out
it needs the record identifier. Get it upstream with Get a record by RemoteID or List records, as in the first scenario above.
Boost.space24

Update a space name

ActionIn the docs only

Renames a space and nothing else, a narrow action that keeps names consistent with the rest of your tools.

When to use it
a client changes its company name in your CRM and its Boost.space space should carry the new one.
Watch out
it only touches the name. Any other change to the space goes through Make an API Call.
Need help

Need help automating Boost.space with Make?

A person reads every message.

FAQ

Boost.space and Make: common questions

01Is the Boost.space Make integration free?
Yes, on the Make side. Boost.space is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans bring the interval down to 1 minute and lift the scenario cap. You still need an active Boost.space account, whose pricing is set by Boost.space itself.
02What do you need to connect Boost.space to Make?
An active Boost.space account and two values from it. The first is the system key, the part of your Boost.space address before .boost.space. The second is an API token, created from your profile under API tokens, with the privileges you choose. In Make, add any Boost.space module, click Create a connection, optionally name it, then paste both values. The connection is then reused by every Boost.space module, so you only go through these steps a single time.
03Do Boost.space triggers in Make react in real time?
No. All 9 Boost.space triggers are scheduled, which means Make checks your account at each scheduled run instead of being notified. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. If a change must travel faster, the answer is a shorter schedule on a paid plan, not a different trigger, since none of the Boost.space ones is instant.
04What if a Boost.space module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Boost.space API with the connection you already set up, so you are not stuck with the 33 listed modules. Keep the Boost.space API reference nearby while you write the request. Also note that Make's documentation for this app is marked as AI-generated and may contain mistakes, so test every new module with Run once and read its bundles before going live.
05Should you use Make or n8n with Boost.space?
It depends on where your team already builds. On Make, Boost.space comes with 33 ready modules, 9 scheduled triggers, a Free plan to start and Make an API Call for the gaps. If your automations already run in n8n, check whether a Boost.space node exists there before moving anything. Neither tool is ranked here: the right choice is the one your team can maintain, with the modules your use case needs.
Same platform

Other docs you might need on this stack.

Browse all integrations