Resources · Make integration

Bonjoro Make integrationAutomate Bonjoro with Make.

Stop copying new contacts into Bonjoro by hand. The Bonjoro Make integration gives you 2 action modules: one creates a task, the other calls the Bonjoro API. This guide shows how to connect your account and build a first working scenario.

Try the Bonjoro integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Bonjoro Make integration do for you?

The Bonjoro Make integration lets Make, a no-code automation tool, add tasks to your Bonjoro account on its own. You build a scenario, which is the automation itself: a chain of modules, each module being one brick that does one job. Something happens in another app, and Bonjoro receives the task without anyone typing it.

Every new signup gets a task. Put the trigger of your signup form or your store first, then Creates a new Bonjoro task. Each new person becomes a task waiting in Bonjoro, so nobody on the team has to watch the form.

Deals that move in your CRM land in Bonjoro. When a deal changes stage in the CRM you already use, the same action module creates the matching task. The CRM stays your source, Bonjoro becomes the to-do list.

Anything the listed module skips goes through Make an API Call. This second module reuses your Bonjoro connection to reach an endpoint of the Bonjoro API directly, for the cases the task module does not cover.

What Make does not give you here: a Bonjoro trigger. Nothing starts a scenario from inside Bonjoro, so the flow always opens on another app or on a schedule. The Make documentation for Bonjoro is also marked as limited, which means fewer ready answers when something breaks; the Make troubleshooting guide covers the common errors of any scenario.

Bonjoro may also be available as an n8n node. If you are weighing the two tools, the n8n vs Make comparison sets out the criteria, and the Make training helps if Make is new to you.

Connect

How do you connect Bonjoro to Make?

  1. 01

    Add a Bonjoro module

    In your scenario, click the +, search for Bonjoro and pick Creates a new Bonjoro task. Make then asks for a connection: your Bonjoro account linked to Make once and reused by both modules. Click Create a connection.

  2. 02

    Name the connection and authorize Make

    Giving the connection a name is optional, but it helps once you run several Bonjoro accounts. Make then sends you to Bonjoro to approve access, or asks for the key Bonjoro gives you. Follow whichever screen appears.

  3. 03

    Save and check the module

    Click Save. The connection now shows in the module, and Make an API Call can pick the same one later without another login. If the module opens with its fields ready to fill, the link works.

First scenario

Your first scenario: turn new contacts into Bonjoro tasks

GoalWhen a new contact appears in another app, Make creates a task for them in Bonjoro.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where new contacts show up, such as your form tool or CRM, and choose its trigger.

  2. 02

    Add the Bonjoro module

    Click the + to the right of that first module, search for Bonjoro and pick Creates a new Bonjoro task. Select the connection you created, or create it now.

  3. 03

    Map the contact data

    Fill the fields Make shows for the task by clicking into each one and choosing data from the first module. A bundle, one item passing between modules, here carries one contact.

  4. 04

    Test with Run once

    Click Run once, then create a test contact in the source app. Read the bundles each module received, and check that the task reached Bonjoro.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What the Bonjoro modules do

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

Bonjoro1

Creates a new Bonjoro task

Action

In Make“Creates a new task in the user's account”

This module puts a new task in your Bonjoro account from data another app sends, so your follow-up list fills itself as contacts arrive.

When to use it
right after the trigger of your form, store or CRM, whenever a new person or a new event should become something your team handles in Bonjoro.
Watch out
it runs once per bundle, so a trigger that returns ten contacts creates ten tasks and spends ten operations. Set up the first module so it only returns the contacts that deserve one.
Bonjoro2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this one you reach any endpoint of the Bonjoro API from your scenario, using the connection you already set up, without writing a separate login.

When to use it
when the task module does not do what you need and the Bonjoro API does. It is the only way to go beyond task creation inside Make.
Watch out
you have to know the endpoint and what it expects, and the Make documentation for Bonjoro is limited, so test each call with Run once before switching the scenario on.
Need help

Need help automating Bonjoro with Make?

A person reads every message.

FAQ

Bonjoro and Make: common questions

01Is the Bonjoro Make integration free?
Yes, on the Make side. Bonjoro is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, limits each run to 5 minutes, handles files up to 5 MB and includes 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations each month, one per module per bundle. Your own Bonjoro subscription is a separate matter, and this page does not cover it.
02What is needed to connect Bonjoro to Make?
A Bonjoro account and a Make account. The Make documentation lists no other prerequisite. You add a Bonjoro module, click Create a connection, optionally name it, then either approve access on the Bonjoro page or paste the key Bonjoro gives you, and click Save. The connection is stored once and both modules reuse it. Since Make marks its Bonjoro documentation as limited, rely on the screens Make actually shows if they differ from this outline, and check the connection by opening a module afterwards.
03Does the Bonjoro Make integration react in real time?
No trigger exists for Bonjoro in Make, so nothing inside Bonjoro can start a scenario. Both modules are actions that run after something else. You start the flow in one of two ways: with the trigger of another app, such as your form tool or CRM, or with a schedule on the first module, every 15 minutes by default. How fast a task appears then depends on that first module: an instant trigger from the other app reacts when its event happens, a scheduled one waits for the next check.
04What if a Bonjoro module is missing in Make?
Use Make an API Call. It lets the scenario reach any endpoint of the Bonjoro API with the connection you already have, which covers what Creates a new Bonjoro task does not. The trade-off is that you work with the API directly: you need to know the endpoint and the data it expects. Make also notes that its Bonjoro documentation is limited because little public information exists, so expect to test each call with Run once before relying on it.
05Should you use Make or n8n for Bonjoro?
It depends on where the rest of your automations already live. In Make, Bonjoro offers task creation plus Make an API Call for anything else, and no trigger. Bonjoro may also have an n8n node, so compare the two on your actual need: which actions you want, which apps feed the flow, and which tool your team already knows. Neither choice changes what the Bonjoro API allows. The comparison page linked above lays out the criteria side by side without a ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations