Resources · Make integration

Businessmap Make integrationAutomate Businessmap with Make.

Can your Kanban board act on its own when a card changes? The Businessmap Make integration gives you 16 modules, including 3 instant triggers on cards. This guide is for teams who run work in Businessmap and want to connect it, then build and switch on a first scenario.

Try the Businessmap integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Businessmap Make integration do?

The Businessmap Make integration links your Businessmap account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, updates or searches something. Once linked, a card that is created, moved or updated can start a scenario, and Make can write cards, comments, subtasks and logged time back into your board.

Onboarding that starts itself. When a request lands as a new card, Watch Card Created fires and Create a Subtask adds the checklist your team always repeats by hand, so nobody starts from a blank card.

Handoffs people actually notice. A card reaching the next stage of the board is a signal. Watch Card Moved catches it, and the rest of the scenario can post a message in another app or drop a Create a Comment note on the card itself.

Time tracking without the extra clicks. If hours are recorded elsewhere, Add a Logged Time to a Card writes them onto the right card, and Get a Card fetches its details first when you need them.

What the integration does not cover: there is no module for boards or users, and the official documentation was unavailable when this page was written, so no limits are listed here. Make an API Call fills the gaps with the same connection. The same app also has a node on the other side, see the Businessmap n8n integration, and the n8n vs Make comparison helps you pick. New to the editor? The Make training covers the basics.

Connect

How do you connect Businessmap to Make?

  1. 01

    Add a Businessmap module

    In a scenario, click the +, search for Businessmap and pick any of its modules. Make then asks for a connection, meaning your Businessmap account linked to Make once and reused by every Businessmap module. Click Create a connection.

  2. 02

    Name it and authorize

    Giving the connection a name is optional, but it helps when you manage several accounts. Then follow what Make shows: either you authorize Make on a Businessmap page, or you paste the key Businessmap gives you.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and Make can list what it reads from your account, such as your workspaces, once you open the module fields.

First scenario

Your first scenario: comment on every new card

GoalWhen a card is created in Businessmap, Make posts a comment on it with the next steps.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas to add the first module.

  2. 02

    Pick the trigger

    Search for Businessmap, choose Watch Card Created and select your connection. This trigger is instant: Businessmap calls Make as soon as a card is created.

  3. 03

    Add the comment

    Click the + on the right of the trigger and add Create a Comment. Map the card from the trigger, then write the text your team should see on each new card.

  4. 04

    Test with Run once

    Click Run once, then create a test card in Businessmap. Open each module to read the bundle it received, meaning the item passed along, here the new card.

  5. 05

    Switch it on

    When the comment shows up on the test card, switch the scenario on. From now on, every new card triggers one run, and each module executed counts as an operation on your plan.

Triggers

What can start a Businessmap scenario?

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

Businessmap1Watch Card Created

Watch Card Created

Instant trigger

In Make“Triggers when a new card is created.”

You get a scenario that reacts the moment someone adds a card to your board, whether it comes from a teammate or an intake form feeding Businessmap. The new card becomes the first bundle, so every later module can reuse its details.

How it fires
instant, Businessmap calls Make through a webhook as soon as the card is created.
When to use it
when new work needs a standard reaction, such as a welcome comment, a set of subtasks or a message to the owner.
Watch out
each new card runs the whole scenario once, so adding many cards in one go uses operations quickly.
Businessmap2Watch Card Moved

Watch Card Moved

Instant trigger

In Make“Triggers when a card is moved.”

This trigger turns a drag on the board into an event Make can act on. Each move sends the card to your scenario, which is how you automate handoffs between stages without anyone writing a status update.

How it fires
instant, Businessmap calls Make through a webhook as soon as the card moves.
When to use it
when reaching a given stage should notify someone, log time or open follow-up subtasks.
Watch out
every move fires it, even the ones you do not care about, and each run uses operations on your plan.
Businessmap3Watch Card Updated

Watch Card Updated

Instant trigger

In Make“Triggers when a card is updated.”

You hear about edits to a card the moment they happen, which keeps a mirror copy in another tool honest. The updated card arrives as a bundle ready to be mapped into the next modules.

How it fires
instant, Businessmap calls Make through a webhook as soon as the card changes.
When to use it
when a spreadsheet, a CRM or a report must reflect the latest version of each card.
Watch out
if your scenario later runs Update a Card on the same card, it can fire this trigger again and loop, so avoid writing back to the card you watch.
Modules

What can Make do in Businessmap?

Businessmap gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Businessmap1

Add a Logged Time to a Card

Action

In Make“Adds a logged time to a card.”

Your hours land on the right card without anyone opening Businessmap to type them. The module records a logged time entry on a card you point to, so reports reflect real effort.

When to use it
when time is captured in another tool, such as a timer app or a form, and must end up on the matching card.
Watch out
map the card carefully, since time logged on the wrong card distorts every report built on it.
Businessmap2

Create a Card

Action

In Make“Creates a card.”

New work shows up on the board by itself. This action creates a card from data coming out of another module, so a request received anywhere becomes a card your team can pull.

When to use it
when a form entry, a support ticket or an email should become work on the board instead of staying in an inbox.
Watch out
if the source can send the same request twice, search with List Cards first to avoid duplicates.
Businessmap3

Create a Comment

Action

In Make“Creates a comment.”

Context reaches the people working the card, right where they already look. This action posts a comment on a card, handy for instructions, links or a summary of what happened in another app.

When to use it
when an event outside Businessmap, such as a paid invoice or a customer reply, should be visible on the related card.
Watch out
comments cannot be removed with the listed modules, so test the text with Run once before switching on.
Businessmap4

Create a Subtask

Action

In Make“Creates a subtask.”

A card gets its checklist without anyone retyping it. This action adds a subtask to an existing card, and a few of them in a row rebuild the standard steps of a recurring process.

When to use it
right after Watch Card Created, when every new card of a type should carry the same steps.
Watch out
each subtask created counts as one operation, so a long checklist costs more on your plan.
Businessmap6

Get a Card

Action

In Make“Gets a card.”

You fetch the full, current details of one card when an earlier module only gave you its reference. The result is a single bundle the next modules can map freely.

When to use it
after a trigger or a comment coming from another app, when you need the card's latest state before deciding what to do.
Watch out
it needs the card's reference, so place it after a module that provides one.
Businessmap7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

You reach any part of the Businessmap API that the listed modules do not cover, with the connection you already set up. It is the way out when a module you need is missing.

When to use it
when you want to act on boards, users or anything else that has no dedicated module here.
Watch out
you write the request yourself, so keep the Businessmap API reference open while you build it.
Businessmap8

Update a Card

Action

In Make“Updates a card.”

A card's details stay in line with what happens elsewhere, without manual edits. This action changes an existing card using values coming from earlier modules.

When to use it
when a status or a date changes in your CRM or support tool and the matching card should follow.
Watch out
pairing it with Watch Card Updated on the same card can make the scenario trigger itself over and over.
Businessmap10

Update a Subtask

Action

In Make“Updates a subtask.”

Progress inside a card moves forward on its own. This action edits a subtask that already exists, for example to mark a step as done when another tool confirms it.

When to use it
when a signature, a payment or a delivery elsewhere means one step of the card is finished.
Watch out
you need the subtask's reference, typically kept from Create a Subtask or read with Get a Card.
Businessmap11

List Cards

Search

In Make“Gets all cards.”

You pull cards out of Businessmap to report on them, sync them or check for duplicates. As a search module, it can return zero, one or many bundles, one per card.

When to use it
before Create a Card to see if the request is already on the board, or to feed a spreadsheet of open work.
Watch out
every card it returns runs the next modules once, so the operation count grows with your board.
Businessmap13

List Workspaces

Search

In Make“Gets all workspaces.”

You get the workspaces your account can reach, one bundle each. It helps a scenario loop through them instead of hard-coding a single workspace in every module.

When to use it
when you manage several workspaces and want a scenario to cover all of them, or to check what the connection actually sees.
Watch out
the result depends on the account behind the connection, so a missing workspace usually means missing access.
Need help

Need help automating Businessmap with Make?

A person reads every message.

FAQ

Businessmap and Make: common questions

01Is the Businessmap Make integration free?
Yes, Businessmap is a standard app in Make, so it works from the Free plan. The Free plan lets you keep 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops a run after 5 minutes and caps files at 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios, bring the minimum interval down to 1 minute and count usage in credits, meaning operations, per month. Your Businessmap subscription is a separate matter.
02What do you need to connect Businessmap to Make?
You need a Businessmap account and a Make account. Add any Businessmap module to a scenario, click Create a connection, optionally name it, then either authorize Make on the Businessmap page or paste the key Businessmap gives you, and click Save. The official documentation lists no extra prerequisite. The connection is created once and reused by all 16 Businessmap modules, so you will not repeat this step for each module you add later.
03Do Businessmap triggers in Make fire in real time?
Yes. All 3 Businessmap triggers, Watch Card Created, Watch Card Moved and Watch Card Updated, are instant: Businessmap calls Make through a webhook as soon as the event happens on a card, so the scenario does not wait for a schedule. In the editor they carry the lightning badge. If you start a scenario from something else, such as a schedule, it runs every 15 minutes by default and you can change that on the first module.
04What if a Businessmap module is missing in Make?
It depends on what you need, but there is a way out. The 16 modules cover cards, comments, subtasks, card links, logged time and workspaces. For anything else in the Businessmap API, such as boards, use Make an API Call: it sends any request with the same connection. The official documentation was unavailable when this page was written, so no limits are listed for this app; test your scenario with Run once before relying on it.
05Should you use Make or n8n for Businessmap?
It depends on the tool your team already works in. Businessmap has an integration in Make with 16 modules, including 3 instant triggers on cards, and it often has a node in n8n too. If your other automations live in Make, staying there keeps every connection in one place. If they live in n8n, the node there is the natural choice. Compare the modules each side offers for your use case rather than picking on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations