Resources · Make integration

MailBluster Make integrationAutomate MailBluster with Make.

Can Make keep your MailBluster leads, orders and products in step with your other tools? Yes. The MailBluster Make integration offers 2 scheduled triggers, 13 actions and 2 searches. This page shows how to link your account and build a first scenario.

Try the MailBluster integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the MailBluster Make integration do for you?

The MailBluster Make integration links your MailBluster account to Make so leads, orders and products move without copy and paste. You build a scenario, the automation itself, from modules: each module is one brick, such as a trigger that watches MailBluster or an action that writes to it.

Signups land in MailBluster on their own. A form or a sales tool in another app sends each new contact to Make, and Create a Lead adds it to MailBluster. When the person comes back with new details, Get a Lead finds them by email and Update a Lead changes the record.

Orders reach the people who need them. Watch Orders picks up each new order and passes it to the next module, one bundle (one item) at a time. From there you can post it to a team channel or a finance sheet in another app. List Orders pulls several at once when you need a batch.

Your product catalog stays in sync. Watch Products reacts to a product added in MailBluster, while Create a Product, Update a Product and Delete a Product let another source drive the catalog.

Both triggers are scheduled: Make checks MailBluster at an interval rather than being called by it. Anything outside the 17 listed modules goes through Make an API Call. To learn the editor step by step, see Make training; plan limits are covered in Make pricing, and if you are still choosing a tool, read n8n vs Make.

Connect

How do you connect MailBluster to Make?

  1. 01

    Create an API key in MailBluster

    In MailBluster, open Brand, then Settings, and click API Keys. Choose Create new, type a name for the key, confirm with Create API key and copy the key shown on screen.

  2. 02

    Add a MailBluster module in Make

    Log in to Make, open your scenario and add any MailBluster module. Click Create a connection. A connection is your MailBluster account linked to Make once, then reused by every MailBluster module.

  3. 03

    Paste the key and save

    You can fill Connection name with a label you will recognize later; the field is optional. Paste the API key you copied from MailBluster, follow the prompts on screen and save. Make can now read and write your MailBluster data.

First scenario

Your first scenario: send new signups to MailBluster

GoalWhen a new signup arrives in another app, Make creates a lead in MailBluster.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. This first module is the app where your signups arrive, a form tool for example.

  2. 02

    Set up the source module

    Search that app by name, pick its module that watches new entries and connect your account. Make then lists the forms or objects it can read, so you select the right one from a menu.

  3. 03

    Add Create a Lead

    Click the + on the right of the first module, search MailBluster and choose Create a Lead. Link your account, then map the details from the previous module into the fields Make displays.

  4. 04

    Test with Run once

    Send a test signup, then click Run once. Make runs the scenario one time and shows the bundles each module received. Open them to check that the lead in MailBluster carries the right data.

  5. 05

    Schedule and switch on

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

Triggers

What starts a MailBluster scenario?

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

MailBluster1Watch Orders

Watch Orders

Scheduled trigger

In Make“Runs when a new orders is created.”

Watch Orders gives your scenario a starting point every time a new order is created in MailBluster. Each order becomes one bundle, so the modules after it handle orders one by one.

How it fires
scheduled. Make checks MailBluster on the scenario's schedule, every 15 minutes by default, and passes on the orders it finds that are new.
When to use it
you want each new order to reach a finance sheet or a team channel without anyone copying it by hand.
Watch out
on the Free plan the shortest interval is 15 minutes, while paid plans go down to 1 minute.
MailBluster2Watch Products

Watch Products

Scheduled trigger

In Make“Runs when a new products is created.”

With Watch Products, a product added to MailBluster is enough to launch your scenario. Make hands over one bundle per new product, ready to be copied elsewhere or announced to your team.

How it fires
scheduled. Make checks MailBluster on the scenario's schedule and picks up the products created since its previous look.
When to use it
MailBluster is where your catalog starts, and another tool, such as a shared sheet, must receive each new item.
Watch out
it reacts to new products only, so a price or name edit on an existing product will not start the scenario.
Modules

What can the MailBluster modules do?

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

MailBluster1

Create a Lead

Action

In Make“Creates a lead.”

This module adds a new lead to MailBluster from data that another module passes along, so contacts collected elsewhere end up in your list without retyping.

When to use it
a signup form, a webinar tool or a CRM in another app produces a new contact and you want it in MailBluster right after.
Watch out
if the person may already exist, run Get a Lead first and route known emails to Update a Lead.
MailBluster2

Create an Order

Action

In Make“Creates an order.”

Create an Order records a sale in MailBluster, so your order history there matches what happened in the tool where the purchase took place.

When to use it
checkout happens in another app and MailBluster should still hold the order, for example to keep its customer view complete.
Watch out
if a scenario also runs Watch Orders on the same account, the orders you create there will show up as new, so plan for it.
MailBluster3

Create a Product

Action

In Make“Creates a product.”

Here you add a product to your MailBluster catalog from a scenario, which saves you from entering each item twice when the catalog is managed in another place.

When to use it
a product appears in your store, a sheet or an inventory tool, and MailBluster needs the same item.
Watch out
before a scenario creates products in bulk, check with List Products that the item is not already there, or you will end up with duplicates.
MailBluster4

Delete a Lead

Action

In Make“Deletes a lead.”

Delete a Lead removes a lead from MailBluster, which helps you honor a removal request raised in another tool without logging in to clean up by hand.

When to use it
a person asks to be forgotten through a form or a support ticket, and the scenario must clear their MailBluster record.
Watch out
a deletion cannot be undone from Make, so test with a dummy lead and Run once before switching the scenario on.
MailBluster5

Delete an Order

Action

In Make“Deletes an order by ID.”

Delete an Order takes an order out of MailBluster using its order ID, keeping your records clean when a sale is cancelled somewhere else.

When to use it
your shop or billing tool flags an order as cancelled and MailBluster should stop showing it.
Watch out
the module needs the order ID, so map it from a trigger or from List Orders; a wrong ID removes the wrong order for good.
MailBluster6

Delete a Product

Action

In Make“Deletes a product.”

When an item leaves your range, Delete a Product removes it from the MailBluster catalog so campaigns and records no longer point to it.

When to use it
a product is retired in your inventory sheet or store, and MailBluster should drop it at the same moment.
Watch out
once the scenario is on, the product goes as soon as the module runs, so test the flow with Run once on a dummy item first.
MailBluster7

Get a Lead

Action

In Make“Gets a lead by lead email.”

Get a Lead looks up one lead in MailBluster from an email address and returns its record, so the next modules can read or reuse its details.

When to use it
before creating a lead, to check whether that email already exists, or before an update, to read what is stored.
Watch out
the lookup works by the lead's email only, so the email must be present in the data the scenario already carries.
MailBluster8

Get an Order

Action

In Make“Gets one order by order ID.”

Get an Order fetches the full record of one order from its order ID, useful when a previous module only passed you the reference.

When to use it
a support ticket or a message mentions an order ID and you want its details in the reply or in a sheet.
Watch out
it reads a single order; to handle many orders, use List Orders, which returns several bundles at once.
MailBluster9

Get a Product

Action

In Make“Gets one product by product ID.”

Get a Product reads one catalog item from MailBluster by its product ID, so a scenario can check the current record before doing anything with it.

When to use it
an update is coming from another tool and you want to compare it with what MailBluster holds before running Update a Product.
Watch out
the product ID is required; if you only know the name, run List Products first and filter the results.
MailBluster10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the MailBluster API with the connection you already set up, covering what the listed modules leave out.

When to use it
you need a MailBluster feature that none of the other listed modules offers, and you are comfortable reading the MailBluster API documentation.
Watch out
you build the request yourself, so start from the MailBluster API documentation and check the response with Run once.
MailBluster11

Update a Lead

Action

In Make“Updates a lead.”

Update a Lead changes an existing lead in MailBluster, so details changed elsewhere show up there without manual edits.

When to use it
a contact updates their profile in your CRM or a form, and MailBluster must reflect the change.
Watch out
the lead has to exist already; find it with Get a Lead and send unknown emails to Create a Lead instead.
MailBluster12

Update an Order

Action

In Make“Updates an order by ID.”

Update an Order edits one order in MailBluster, found by its order ID, so the record follows what really happened to the sale.

When to use it
a refund, a partial return or a correction is logged in your billing tool, and MailBluster needs the same version.
Watch out
map the order ID from the source rather than typing it, otherwise every run edits the same order.
MailBluster13

Update a Product

Action

In Make“Updates a product.”

Update a Product rewrites an item of your MailBluster catalog, keeping it aligned with the tool where you actually manage your products.

When to use it
your inventory sheet is the reference and each change there should reach MailBluster.
Watch out
Watch Products only fires on new products, so it will not notice these edits; start this flow from the tool where the change happens.
MailBluster14

List Orders

Search

In Make“Gets list of orders.”

List Orders pulls a set of orders from MailBluster in one go, returning zero, one or several bundles that the next modules handle one after the other.

When to use it
you need an export of past orders into a sheet, or you are hunting for an order ID before an update.
Watch out
each returned order runs the following modules once, so a long list uses many operations.
MailBluster15

List Products

Search

In Make“Gets list of products.”

List Products returns the items of your MailBluster catalog as separate bundles, a quick way to copy or review the whole range from a scenario.

When to use it
you want to rebuild a product sheet, or find a product ID from its name before using Get a Product.
Watch out
each product returned runs the next modules once, so a large catalog uses many operations.
Need help

Need help automating MailBluster with Make?

A person reads every message.

FAQ

MailBluster and Make: common questions

01Is the MailBluster Make integration free?
Yes, MailBluster is a standard app in Make, so you can use it from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. You still need an active MailBluster account, whose subscription is priced by MailBluster itself.
02What do you need to connect MailBluster to Make?
You need two things: an active MailBluster account and an API key. Create the key in MailBluster under Brand, then Settings, then API Keys, with Create new and Create API key, and copy it from the screen. In Make, add a MailBluster module, click Create a connection, optionally name it, and paste the key. That one connection then serves every MailBluster module in all your scenarios, so you only do this once per account.
03Are MailBluster triggers in Make scheduled or instant?
Scheduled. Watch Orders and Watch Products do not receive a call from MailBluster; Make checks your account on the schedule of the scenario, every 15 minutes by default. On the Free plan you cannot go below 15 minutes, and paid plans allow checks as often as every minute. There is no instant MailBluster trigger in the catalog, so a new order or product is processed at the next check rather than the moment it is created.
04What if the MailBluster module you need is missing in Make?
It depends on the feature, but you have a way out. The 17 modules cover leads, orders and products, and Make an API Call reaches any other endpoint of the MailBluster API with the same connection. You write the request from the MailBluster API documentation and test it with Run once. The Make documentation for this app is generated from vendor docs and may contain mistakes, so confirm important details with MailBluster directly.
05Should you use Make or n8n for MailBluster?
It depends on the criteria that matter to you. On Make, MailBluster comes with 17 ready modules, including 2 scheduled triggers and Make an API Call, and it is available from the Free plan. If you already run n8n, check whether a MailBluster node exists there and what it covers before you decide. Compare the modules each side offers for leads, orders and products, the editor your team prefers, and the plan limits that apply to your volume.
Same platform

Other docs you might need on this stack.

Browse all integrations