Resources · Make integration

Boldem Make integrationAutomate Boldem with Make.

Can Boldem react on its own when a customer clicks, buys or opts out? The Boldem Make integration gives you 60 modules, 5 of them triggers. This guide covers the connection, a first scenario and what each module is good for.

Try the Boldem integration on MakeSee the 60 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Boldem Make integration automate?

The Boldem Make integration links your Boldem account to Make, a no-code tool where you build a scenario (the automation itself: a chain of modules, each one a brick that watches, acts or searches). Boldem then trades contacts, carts, orders, coupons and e-mail events with your other apps, and nobody copies data by hand.

Warm leads from clicks. Watch Transactional E-mail Click spots a recipient who clicked, and Insert Contact into Automation drops that person into the Boldem sequence you already built. A software company can nurture trial users this way, based on what they actually opened and clicked.

A cleaner list after complaints. Watch Transactional E-mail Marked as Spam, paired with Update Contact or Create Unsubscribe, keeps people who complained out of your next sends, which protects the whole list.

Shop data inside Boldem. Create Order, Create Product and Create Cart copy what happens in your store into Boldem, so your e-mails can speak about real purchases. Create Coupon then hands a discount to the right buyer.

Two limits to know before you start. The 5 Boldem triggers are all scheduled: Make checks Boldem on the scenario's schedule, it is never called the instant an e-mail is clicked. And the connection needs a paid Boldem Profi plan. The Make review gives a wider picture of the tool, and Make pricing explains what counts on your plan.

If you also look at n8n, check whether it offers a Boldem node for your use case, then compare both tools with n8n vs Make.

Connect

How do you connect Boldem to Make?

  1. 01

    Create an API key in Boldem

    In Boldem, open Settings > API and click New API key. Give the key a name you will recognize later. If Boldem asks for a callback URI, paste https://www.integromat.com/oauth/cb/boldem.

  2. 02

    Copy the two credentials

    Boldem then shows a window with a Client ID and a Client secret. Copy both somewhere safe right away: Make asks for them in the next step, and they are what lets Make act on your account.

  3. 03

    Create the connection in Make

    Add any Boldem module to a scenario and click Create a connection. The Connection name is optional, but a clear name helps when you run several accounts. Paste the credentials or follow the on-screen steps, and the connection is ready for every Boldem module.

First scenario

Your first scenario: turn an e-mail click into a nurture sequence

GoalWhen someone clicks a link in a Boldem transactional e-mail, Make adds that contact to one of your Boldem automations.

  1. 01

    Create the scenario

    On the Scenarios page of Make, create a new scenario and click the big +. That empty circle becomes the first module, the one that starts everything.

  2. 02

    Add the click trigger

    Search for Boldem, pick Watch Transactional E-mail Click and click Create a connection if you have not linked the account yet. Fill the fields the module shows you.

  3. 03

    Add the automation module

    Click the + on the right of the trigger, pick Insert Contact into Automation, and map into it the data from the trigger that points to the person who clicked.

  4. 04

    Test with Run once

    Click a link in a test e-mail, then press Run once. Open the bubble above each module to read the bundle it received (one bundle is one item, here one click) and check that the right contact came through.

  5. 05

    Set the schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; the Free plan stops at that interval, paid plans go down to 1 minute. Switch the scenario on.

Triggers

What can start a Boldem scenario?

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

Boldem1Watch Transactional E-mail Click

Watch Transactional E-mail Click

triggerIn the docs only

Starts your scenario when a recipient clicks a link in a transactional e-mail sent through Boldem, so a click turns into a next step instead of a line in a report.

How it fires
scheduled. Make checks the app on the scenario's schedule (every 15 minutes on a new scenario), so the click appears at the next check, not the second it happens.
When to use it
a click on an onboarding or order e-mail should move that person to sales or into a Boldem automation.
Watch out
click a real test link before Run once, then read the bundle to see what the trigger carries.
Boldem2Watch Transactional E-mail Delivery

Watch Transactional E-mail Delivery

triggerIn the docs only

Gives you a bundle for each transactional e-mail Boldem reports as delivered, which is the proof you need before telling anyone a message reached its inbox.

How it fires
scheduled. Make checks the app on the scenario's schedule, so deliveries pile up between two checks and come in together.
When to use it
log that an invoice or a password e-mail reached the customer, in a spreadsheet or your support tool.
Watch out
every delivery is one bundle and each module after it spends one operation per bundle, which adds up fast on a busy sender.
Boldem3Watch Transactional E-mail Marked as Spam

Watch Transactional E-mail Marked as Spam

triggerIn the docs only

Catches the recipients who flagged one of your transactional e-mails as spam, so you can stop writing to them before the complaints hurt your sending.

How it fires
scheduled. Make checks the app on the scenario's schedule, which means the complaint reaches your scenario at the next check rather than right away.
When to use it
pair it with Create Unsubscribe or Update Contact so a complaint removes the person from future sends.
Watch out
keep this scenario switched on; with the Free plan's limit of 2 active scenarios, it is a good candidate for one of them.
Boldem4Watch Transactional E-mail Opening

Watch Transactional E-mail Opening

triggerIn the docs only

Hands you each opening of a transactional e-mail, a lighter signal than a click but a useful sign that a customer actually saw the message.

How it fires
scheduled. Make checks the app on the scenario's schedule and picks up the openings recorded since the last check.
When to use it
a quote or a renewal notice was opened, and your sales rep should hear about it in the team chat.
Watch out
one person can open the same e-mail several times, so filter or deduplicate before you alert a colleague on every bundle.
Boldem5Watch Transactional E-mail Unsubscribe

Watch Transactional E-mail Unsubscribe

triggerIn the docs only

Tells your scenario who unsubscribed from a transactional e-mail, so the opt-out can travel to your CRM and your other sending tools, not only Boldem.

How it fires
scheduled. Make checks the app on the scenario's schedule, so the unsubscribe reaches your other apps after the next check.
When to use it
your sales team writes from a separate tool and must stop contacting people who opted out in Boldem.
Watch out
the gap between two checks is real; if another tool sends in the meantime, that person may still receive one message.
Modules

What can Make do in Boldem?

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

Boldem1

Create Cart

ActionIn the docs only

Puts a shopping cart into Boldem from data your scenario already holds, so your e-mails know what a visitor was about to buy.

When to use it
a basket is built on a shop Make can read, and Boldem should keep it for follow-up e-mails.
Watch out
each run adds a cart; for a basket that already exists in Boldem, pick Update Cart.
Boldem2

Create Contact

ActionIn the docs only

Adds a new person to your Boldem audience, fed by whatever app captured them first: a form, a CRM, a checkout page.

When to use it
a lead signs up somewhere outside Boldem and should be ready for your next campaign.
Watch out
if the person may already be in Boldem, run Get Contact by E-mail first and route existing contacts to Update Contact.
Boldem3

Create Coupon

ActionIn the docs only

Generates a single coupon in Boldem, so a discount can be handed out by a scenario instead of typed in by someone on your team.

When to use it
a first order or a survey answer should earn the customer a reward they can use right away.
Watch out
for a large batch of codes, Import Coupons in Bulk saves you one operation per coupon.
Boldem4

Create Coupon Group

ActionIn the docs only

Sets up a coupon group in Boldem, the container that keeps the coupons of one campaign together and easy to track.

When to use it
a new promotion starts and you want its coupons separated from last season's before any code is created.
Watch out
create the group before the coupons, then map its reference into Create Coupon or Import Coupons in Bulk.
Boldem5

Create Mailing List

ActionIn the docs only

Opens a fresh mailing list in Boldem from a scenario, which is handy when lists follow events, webinars or product launches.

When to use it
a new event is published in your calendar or project tool and deserves its own list of attendees.
Watch out
each run creates a new list; if it may already exist, check first with List Mailing Lists.
Boldem6

Create Order

ActionIn the docs only

Writes a purchase into Boldem, so your campaigns can target buyers based on what they really ordered and not on guesses.

When to use it
your shop or invoicing tool confirms a sale and Boldem should record it for post-purchase e-mails.
Watch out
test on one order with Run once before switching on, so a mapping error does not flood Boldem with incomplete orders.
Boldem7

Create Product

ActionIn the docs only

Adds an item to the Boldem product catalog, so product e-mails and recommendations can refer to what you actually sell.

When to use it
a new reference goes live in your store or inventory sheet and Boldem should know it too.
Watch out
to change an item already in Boldem, Update Product is the right module, not a second Create Product.
Boldem8

Create Subscribe Request

ActionIn the docs only

Records a subscribe request in Boldem, the step where someone asks to receive your e-mails, sent from a form or app outside Boldem.

When to use it
a checkbox on your checkout or event form collects consent and Boldem should take it from there.
Watch out
only send people who really asked; this module records a request, it does not create consent on its own.
Boldem9

Create Unsubscribe

ActionIn the docs only

Adds a person to the Boldem unsubscribe records, so an opt-out collected in another tool is respected in Boldem as well.

When to use it
a customer asks your support team to stop the e-mails, and the ticket tool should pass that request to Boldem.
Watch out
reversing it takes Delete Unsubscribe, so keep this module behind a clear condition.
Boldem10

Create and Send Transactional E-mail with Template

ActionIn the docs only

Sends a one-to-one e-mail from Boldem built on one of your templates, filled with data from earlier modules: an order, a name, a link.

When to use it
a booking, a signup or a payment happens in another app and the customer needs a confirmation right after.
Watch out
the template must exist in Boldem first; test with your own address in Run once before real customers get it.
Boldem11

Create and Send Transactional SMS

ActionIn the docs only

Sends a text message through Boldem to one person, for the cases where an e-mail would be read too late.

When to use it
a delivery is on its way, an appointment is confirmed, or a code has to reach the customer on their phone.
Watch out
a looping scenario sends one SMS per bundle; check with Run once how many bundles reach this module.
Boldem12

Delete Cart

ActionIn the docs only

Removes a cart from Boldem, which keeps abandoned-cart e-mails from chasing a basket that is no longer relevant.

When to use it
the customer finally paid, or the cart was cancelled in your shop, and Boldem should forget it.
Watch out
treat a deletion as final; put a filter before this module so only the carts you mean to remove reach it.
Boldem13

Delete Contact

ActionIn the docs only

Erases a contact from Boldem when you already hold the reference of that record, for example from Get Contact or List Contacts.

When to use it
a customer asks for their data to be removed and your process has to clear Boldem too.
Watch out
deletion is not an opt-out; for someone who only wants fewer e-mails, Create Unsubscribe fits better.
Boldem14

Delete Contact by E-mail

ActionIn the docs only

Removes a contact from Boldem using only their e-mail address, the one detail every other app usually has.

When to use it
a deletion request arrives by form or ticket with just an address, and no Boldem reference in sight.
Watch out
a typo in the mapped address targets the wrong person or nobody; check the value in Run once before switching on.
Boldem15

Delete Coupon

ActionIn the docs only

Withdraws a single coupon from Boldem, so a code that should no longer work stops circulating in your campaigns.

When to use it
a reward was granted by mistake, or an order was refunded and its code must go.
Watch out
you need the coupon's reference; List Coupons or Get Coupon placed before this module gives it to you.
Boldem16

Delete Coupon Group

ActionIn the docs only

Clears out a whole coupon group in Boldem, useful when a promotion is over and its container only adds noise.

When to use it
a campaign ends in your planning tool and its coupon group should leave Boldem at the same time.
Watch out
make sure no live campaign still hands out codes from that group before the scenario deletes it.
Boldem17

Delete Mailing List

ActionIn the docs only

Removes a mailing list from Boldem, so old event or test lists stop cluttering the screen where you pick recipients.

When to use it
an event is archived in your project tool and its dedicated list has no use any more.
Watch out
run List Mailing Lists first and filter on the exact list, because a wrong mapping deletes a list you still need.
Boldem18

Delete Order

ActionIn the docs only

Takes an order out of Boldem, so e-mails based on purchase history no longer count a sale that did not happen.

When to use it
an order is cancelled or voided in your shop and Boldem should reflect it.
Watch out
for a partial change such as a new status, Update Order keeps the history instead of wiping it.
Boldem19

Delete Product

ActionIn the docs only

Drops a product from the Boldem catalog, keeping your e-mails from promoting something you no longer sell.

When to use it
an item is discontinued in your store or stock sheet and should vanish from Boldem too.
Watch out
an item that is only out of stock may come back; Update Product can be the gentler choice there.
Boldem20

Delete Unsubscribe

ActionIn the docs only

Lifts an unsubscribe record in Boldem, so someone who opted out and later changed their mind can receive your e-mails again.

When to use it
a customer explicitly asks to be put back on your e-mails through a form or your support team.
Watch out
only run it on a clear, recorded request; putting someone back without consent is exactly what opt-outs protect against.
Boldem21

Get Cart

ActionIn the docs only

Fetches one cart from Boldem and hands its details to the next modules, for example to rebuild a reminder elsewhere.

When to use it
a scenario already knows which cart it is about and needs its content before deciding what to send.
Watch out
Get Cart reads one known cart; to browse carts, List Carts returns several bundles.
Boldem22

Get Contact

ActionIn the docs only

Pulls the full Boldem record of a contact you already have a reference for, so later modules can use what Boldem knows about them.

When to use it
an earlier module returned a contact reference and your CRM needs the rest of the details.
Watch out
if all you have is an address, Get Contact by E-mail is the module that fits.
Boldem23

Get Contact by E-mail

ActionIn the docs only

Looks up a Boldem contact from an e-mail address, the easiest way to check whether a person is already in your audience.

When to use it
before Create Contact, to see whether a new record is needed or an existing one should be updated.
Watch out
run a test with an address that is not in Boldem to see what the module returns, and plan the scenario around it.
Boldem24

Get Coupon

ActionIn the docs only

Reads one coupon from Boldem, handy when a scenario must confirm what a code is before telling a customer about it.

When to use it
a support ticket mentions a coupon and the answer should include what Boldem has on file.
Watch out
it needs the coupon's reference; List Coupons helps when you do not have it yet.
Boldem25

Get Coupon Group

ActionIn the docs only

Retrieves the details of one coupon group, so your scenario can check a campaign's container before adding or removing codes.

When to use it
before Import Coupons in Bulk, to confirm the group you are about to fill is the right one.
Watch out
to find a group by browsing rather than by reference, start with List Coupon Groups.
Boldem26

Get Mailing List

ActionIn the docs only

Brings back one Boldem mailing list, so a scenario can check its details before sending contacts into it.

When to use it
a form picks a list per topic and you want to confirm the list still exists before the next step.
Watch out
if the list may have been deleted meanwhile, test that case with Run once so a missing list does not surprise you later.
Boldem27

Get Order

ActionIn the docs only

Reads a single order stored in Boldem, useful for matching it with what your shop or accounting tool says.

When to use it
a refund is processed elsewhere and the scenario must find the Boldem order before updating or deleting it.
Watch out
Get Order works on one known order; for a set of orders, use List Orders.
Boldem28

Get Product

ActionIn the docs only

Fetches one product from the Boldem catalog, so another app can compare it with its own data before anything changes.

When to use it
your inventory sheet flags a change and you want to see the Boldem version before running Update Product.
Watch out
to scan the whole catalog, List Products returns one bundle per product and each one costs an operation downstream.
Boldem29

Get Subscribe Request

ActionIn the docs only

Reads one subscribe request from Boldem, which helps when you need to know where a person stands before writing to them.

When to use it
a customer tells support they signed up but get nothing, and the scenario checks their request.
Watch out
you need the request's reference; List Subscribe Requests is the way in when you do not have it.
Boldem30

Get Transactional E-mail

ActionIn the docs only

Opens the Boldem record of one transactional e-mail, so a scenario can report on a specific message instead of guessing.

When to use it
a customer says the invoice never arrived and your help desk needs the facts in the ticket.
Watch out
run it once on a real message and read the bundle to see which details Boldem returns.
Boldem31

Get Transactional SMS

ActionIn the docs only

Reads one transactional SMS sent through Boldem, giving your scenario the record of that specific text message.

When to use it
a customer disputes an appointment reminder and your team wants the Boldem record next to the booking.
Watch out
it covers one message you can point to; List Transactional SMS is the module for a wider look.
Boldem32

Get Unsubscribe

ActionIn the docs only

Checks one unsubscribe record in Boldem, the quickest way to confirm an opt-out before any other tool writes to that person.

When to use it
your sales tool is about to e-mail a lead and the scenario checks Boldem first.
Watch out
make sure the scenario acts on the answer, so an opted-out person really stops the flow instead of just being logged.
Boldem33

Import Contacts in Bulk

ActionIn the docs only

Sends many contacts to Boldem in one go instead of one module run per person, which keeps big imports tidy and cheaper in operations.

When to use it
a fair, a webinar or a partner hands you a full list and it all belongs in Boldem.
Watch out
gather the rows with an aggregator before this module, otherwise it runs once per bundle.
Boldem34

Import Coupons in Bulk

ActionIn the docs only

Loads a whole batch of coupons into Boldem in a single run, the practical route when a campaign needs many codes.

When to use it
a partner or your shop generated codes in a sheet and they should all land in one coupon group.
Watch out
aggregate the codes first, and create the target group with Create Coupon Group if it does not exist.
Boldem35

Import Unsubscribes in Bulk

ActionIn the docs only

Pushes a full list of opt-outs into Boldem at once, so every refusal kept in another tool applies here too.

When to use it
you move to Boldem from another e-mail tool and must bring its unsubscribe list along.
Watch out
run the import before the first campaign leaves Boldem, not after, or old opt-outs receive it.
Boldem36

Insert Contact into Automation

ActionIn the docs only

Enrolls a contact in one of your existing Boldem automations, so a sequence you designed in Boldem starts from an event in any app.

When to use it
a trial starts, a quote is accepted or a link is clicked, and the matching nurture sequence should begin.
Watch out
the automation has to exist and be set up in Boldem first; Make only places the contact in it.
Boldem37

List Carts

SearchIn the docs only

Returns the carts stored in Boldem as separate bundles, one per cart, ready for filtering or reporting in another app.

When to use it
you want to push open carts to a sheet or a dashboard for the sales team.
Watch out
the search can return zero, one or many carts, and every module after it runs once per cart.
Boldem38

List Contacts

SearchIn the docs only

Retrieves your Boldem contacts as a stream of bundles, the starting point for syncing them to a CRM or cleaning your audience.

When to use it
you set up a sync between Boldem and your CRM and need every existing contact once.
Watch out
on a big audience each bundle costs an operation in the next modules; test on a small result first.
Boldem39

List Coupon Groups

SearchIn the docs only

Shows every coupon group in Boldem as one bundle each, so a scenario can pick the right campaign by name.

When to use it
you receive a campaign name from a form and need the matching group before importing codes.
Watch out
add a filter on the name right after it, or the next modules run for every group.
Boldem40

List Coupons

SearchIn the docs only

Lists the coupons held in Boldem, so you can audit which codes exist or find one to update or remove.

When to use it
finance wants a sheet of all coupons issued for a campaign.
Watch out
the search can return nothing; a scenario built on it should not assume a code is always there.
Boldem41

List Mailing Lists

SearchIn the docs only

Gets you every mailing list of your Boldem account as separate bundles, so the rest of the scenario can pick the right audience by its name instead of a value typed by hand.

When to use it
you add a new signup source and want the scenario to find the list it should feed before creating the contact.
Watch out
a search module can return zero, one or many bundles; add a filter after it so only the list you expect moves on.
Boldem42

List Orders

SearchIn the docs only

Brings back the orders stored in Boldem, one bundle per order, which lets you read your shop history from a scenario and push it into a sheet, a report or another tool.

When to use it
a finance or sales teammate asks for the orders in a spreadsheet and you would rather not export them manually.
Watch out
each order found costs one operation in the next modules, since Make counts one execution per bundle.
Boldem43

List Products

SearchIn the docs only

Pulls the product catalog you keep in Boldem into the scenario, one product per bundle, ready to compare with the catalog of your online store or your inventory tool.

When to use it
you suspect the products in Boldem have drifted from those in your store and want a scenario that spots the gaps.
Watch out
if nothing matches, the module returns no bundle and the modules after it simply do not run.
Boldem44

List Subscribe Requests

SearchIn the docs only

Shows you the subscribe requests recorded in Boldem, each one as its own bundle, so you can follow who asked to join a list before they become a full contact.

When to use it
a marketing manager wants to see the pending requests of a campaign landing page in the team's shared tracker.
Watch out
follow it with Update Contact or another module only after a filter, otherwise every request found goes through.
Boldem45

List Transactional E-mails

SearchIn the docs only

Returns the transactional e-mails Boldem has sent, one bundle each, which gives you a way to audit order confirmations or password resets from outside Boldem.

When to use it
support needs to check whether a customer really received a message before answering a ticket.
Watch out
for a single known message, Get Transactional E-mail keeps the scenario lighter than a full list.
Boldem46

List Transactional SMS

SearchIn the docs only

Collects the transactional text messages sent through Boldem, one bundle per SMS, so you can log them next to the rest of your customer history.

When to use it
your team wants every SMS sent to a customer visible in the CRM, not only inside Boldem.
Watch out
the SMS version and the e-mail version are two separate modules; pick this one only for text messages.
Boldem47

List Unsubscribes

SearchIn the docs only

Hands you the list of unsubscribes held in Boldem, one bundle each, which is what you need to keep other tools from writing to people who opted out.

When to use it
you sync contacts toward a second mailing tool and want to exclude everyone who left your lists in Boldem.
Watch out
treat this data with care: sending again to these addresses goes against what the person asked.
Boldem48

Make an API Call

ActionIn the docs only

Lets you call any endpoint of the Boldem API from your scenario, reusing the connection you already created, so what the listed modules do not cover stays within reach.

When to use it
none of the 60 listed modules covers the action you need, and the Boldem API does.
Watch out
you write the request yourself here, so keep the Boldem API documentation open next to the editor.
Boldem49

Update Cart

ActionIn the docs only

Changes a cart that already exists in Boldem instead of creating a second one, so the data behind your abandoned cart e-mails stays accurate.

When to use it
a shopper adds or removes an item in your store and Boldem should hold the new version of the cart.
Watch out
map the cart from a previous module, such as List Carts or Get Cart, rather than typing it.
Boldem50

Update Contact

ActionIn the docs only

Rewrites the details of a contact already in Boldem, which keeps one clean record per person instead of duplicates piling up.

When to use it
a customer changes their details in your CRM or shop, and Boldem needs the same version before the next campaign.
Watch out
if the contact might not exist yet, look it up first with Get Contact by E-mail and branch the scenario.
Boldem51

Update Coupon

ActionIn the docs only

Edits a coupon you already created in Boldem, so a promotion can evolve without deleting and recreating the code your customers know.

When to use it
your sales team extends an offer and the coupon in Boldem must follow the new terms.
Watch out
this module changes one coupon; to change the group that holds it, use Update Coupon Group.
Boldem52

Update Coupon Group

ActionIn the docs only

Edits a coupon group that already exists in Boldem, the container of one campaign, without deleting and rebuilding it when the campaign changes.

When to use it
a seasonal campaign is reshaped and the group that holds its codes needs new settings.
Watch out
fetch the group first with List Coupon Groups or Get Coupon Group, so you target the right one before switching the scenario on.
Boldem53

Update Mailing List

ActionIn the docs only

Edits a mailing list that already exists in Boldem, so your lists stay tidy as your audiences evolve, without rebuilding them from scratch.

When to use it
a product line changes in your store and the list tied to it in Boldem should follow.
Watch out
find the list first with List Mailing Lists or Get Mailing List and map it here.
Boldem54

Update Order

ActionIn the docs only

Updates an order already stored in Boldem, so what Boldem knows about a purchase matches what happened in your store after checkout.

When to use it
an order is refunded or modified in your e-commerce tool and Boldem should reflect it for the next e-mails.
Watch out
pair it with a trigger or a search from your store app; a mistyped order breaks the link.
Boldem55

Update Product

ActionIn the docs only

Edits a product already in your Boldem catalog, so your e-mails show the item as it is in your store.

When to use it
a product sheet is edited in your shop and the version inside Boldem is now out of date.
Watch out
run the scenario once with Run once on a single product before letting it touch the whole catalog.
Need help

Need help automating Boldem with Make?

A person reads every message.

FAQ

Boldem and Make: frequent questions

01Is the Boldem Make integration free?
Yes on the Make side. Boldem is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, scheduled runs at most every 15 minutes, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Each module that runs on a bundle counts as one operation. Paid Make plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. On the Boldem side, the connection needs a paid Profi plan.
02What do you need to connect Boldem to Make?
A Boldem account on the paid Profi plan and a Make account. In Boldem, go to Settings, then API, click New API key and name it. If Boldem asks for a callback URI, use the one Make gives in its documentation. Copy the Client ID and the Client secret shown in the window. In Make, add a Boldem module, click Create a connection, give it a name if you like and paste the credentials. Every Boldem module then reuses that connection.
03Do the Boldem triggers in Make work in real time?
No. The 5 Boldem triggers are scheduled: Make checks Boldem at the interval set on the scenario, and there is no instant trigger for this app. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans go down to 1 minute. Clicks, openings or unsubscribes that happen between two checks arrive together at the next one, each as its own bundle.
04What if the Boldem module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Boldem API from inside the scenario, with the same connection as the other modules, so you are not limited to the 60 listed ones. It asks you to read the Boldem API documentation to know what to send. Also note that the Make documentation for Boldem is flagged as AI-generated, so check important details with Boldem directly before relying on them.
05Should you use Make or n8n for Boldem?
It depends on what your scenario needs. In Make, Boldem comes with 60 modules covering contacts, carts, orders, products, coupons, lists and transactional messages, with 5 scheduled triggers and Make an API Call for the rest. Before choosing n8n, check whether it offers a Boldem node and whether that node covers the operations you plan to use. Compare both tools on those modules and on the plan limits that apply to your volume, not on general impressions.
Same platform

Other docs you might need on this stack.

Browse all integrations