Resources · Make integration

BulkGate Make integrationAutomate BulkGate with Make.

Can your SMS and Viber messages go out on their own when something happens elsewhere? The BulkGate Make integration gives you 26 modules: 2 triggers and 24 actions. This guide connects your account, builds a first scenario and explains when to pick each module.

Try the BulkGate integration on MakeSee the 26 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the BulkGate Make integration let you automate?

The BulkGate Make integration links your BulkGate account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick: it sends an SMS or a Viber message, handles a one-time code, updates a contact or watches delivery reports, without you opening BulkGate.

Confirm an order by text. A sale lands in your shop or CRM, Make passes the customer's number to Send a Notification SMS Message, and the buyer gets a confirmation. If the customer prefers Viber, Send a Notification Viber Message covers the same job on that channel.

Secure a sign-in with a code. Send an OTP via SMS sends a one-time code, Verify an OTP checks what the user typed, and Resend an OTP handles the person who never got it. Your app keeps the login screen; Make does the messaging part.

Keep your audience list clean. Add a Contact and Import Contacts feed your BulkGate address book, while Blacklist a Number records people who asked to stop. Before a campaign goes out, Is Number Blacklisted lets the scenario skip them.

Where the listed modules stop, Make an Api Call reaches the rest of the BulkGate API through the same connection. The documentation Make publishes for this app is flagged as AI-generated, so double-check anything critical with BulkGate. If you are weighing tools, read n8n vs Make, and the Make pricing page explains how operations are counted. For hands-on help, the Make agency team builds scenarios like these.

Connect

How do you connect BulkGate to Make?

  1. 01

    Create your API access in BulkGate

    Log in to BulkGate, open Modules and APIs, click the API you want, then Create API. BulkGate displays the Client ID and the API token. Copy both right away, Make asks for them in the next step.

  2. 02

    Add a BulkGate module in Make

    In your scenario, click the +, search for BulkGate and pick any module. Click Create a connection. The Connection name field is optional; a clear label like the account's purpose helps once you own several.

  3. 03

    Paste the credentials and save

    Enter the ID and token copied from BulkGate, or follow the instructions Make shows on screen, and save. That connection (your BulkGate account linked to Make once) is then reused by every BulkGate module in your scenarios.

First scenario

Your first scenario: welcome every new customer by SMS

GoalWhen a new customer signs up in another app, Make saves the person in BulkGate and sends them a welcome SMS.

  1. 01

    Create the scenario

    Go to the Scenarios page, click Create a new scenario, then click the big + to place the first module. This first module is the app where your new customers come from, such as your form or CRM.

  2. 02

    Add Add a Contact

    Click the + on the right of the first module, search BulkGate and choose Add a Contact. Pick your connection, then map the name and phone number that arrive from the first module.

  3. 03

    Chain the welcome SMS

    Add Send a Notification SMS Message after the contact. Map the phone number again and write the text, mixing plain words with the customer's first name dragged in from earlier modules.

  4. 04

    Test with Run once

    Click Run once and create a test customer with your own number. Each module shows the bundles it received (one bundle is one item, here one customer), so you can see what reached BulkGate.

  5. 05

    Schedule and switch it on

    Open the clock on the first module: a new scenario runs every 15 minutes by default. Keep that or change it, then switch the scenario on. The free plan allows 2 active scenarios.

Triggers

BulkGate triggers: what starts your scenario

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

BulkGate1Watch Bulk Delivery Reports

Watch Bulk Delivery Reports

triggerIn the docs only

This trigger brings the delivery reports of your bulk campaigns into Make, so the scenario can act on what happened after a mass send instead of you checking the BulkGate dashboard.

How it fires
it is a scheduled trigger, so Make checks BulkGate on the scenario's schedule, every 15 minutes by default, and never faster than that interval on the free plan.
When to use it
after a promotion sent with one of the marketing modules, to log each result in a sheet or alert your team about numbers that failed.
Watch out
the type comes from the module name, as Make's documentation gives no description; run it once to see what a report bundle contains.
BulkGate2Watch Delivery Reports

Watch Delivery Reports

triggerIn the docs only

Judging by its name, this one covers the reports of messages sent one at a time, like notifications and codes, so a scenario can follow up when a text did not land.

How it fires
scheduled, which means Make checks the app on the scenario's schedule rather than being called by BulkGate the second a report appears.
When to use it
when an order confirmation matters enough that a failed SMS should trigger an email or a Viber message instead.
Watch out
the split between single and bulk reports is read from the two module names, as the documentation describes neither; check with Run once which one your sends show up in.
Modules

Everything the BulkGate modules can do

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

BulkGate1

Add a Contact

ActionIn the docs only

Your BulkGate address book gains one person each time the module runs, fed by whatever app came before it. That keeps your SMS audience in sync with the place where customers really sign up.

When to use it
right after a form submission or a new CRM record, for one person at a time.
Watch out
for a whole file of people, Import Contacts fits better than looping this module.
BulkGate2

Blacklist a Number

ActionIn the docs only

A phone number goes on your BulkGate blacklist, so future sends can leave that person alone. It turns an opt-out request into a recorded rule instead of a note someone may forget.

When to use it
when a customer replies STOP in another tool or unticks marketing consent in your CRM.
Watch out
pair it with Is Number Blacklisted before your campaigns, so the list is actually checked.
BulkGate3

Check Credit Balance

ActionIn the docs only

With this module the scenario learns how much credit remains on your BulkGate account, which lets you react before a campaign stalls halfway for lack of funds.

When to use it
as the first step of a large send, followed by a filter that stops the run and alerts you when the balance looks too low.
Watch out
it reads the balance, it does not top it up.
BulkGate4

Check Delivery Report

ActionIn the docs only

One specific message gets its delivery status looked up on demand, rather than waiting for a trigger to report it. Handy when a scenario must know right now whether a text arrived.

When to use it
a few modules after a send, before deciding whether to fall back to Viber or email.
Watch out
the module has to know which message to look up, so map what the send module returned about it.
BulkGate5

Edit Shortened URL

ActionIn the docs only

A short link you already created through BulkGate can be changed without sending a new one, so the messages already in your customers' phones point to the updated page.

When to use it
when a landing page moves or a promotion page is replaced after the campaign has gone out.
Watch out
you need the short link's reference from Shorten an URL, so store it somewhere the scenario can read.
BulkGate6

Edit a Contact

ActionIn the docs only

Changes made elsewhere, a new phone number or a corrected name, flow into the matching BulkGate contact. Your SMS list stops drifting away from the CRM that the sales team actually updates.

When to use it
after a customer updates their profile in your shop or support tool.
Watch out
the scenario must know which contact to change, so run Get a Contact first when you only have the number.
BulkGate7

Get a Contact

ActionIn the docs only

This one reads a single contact from BulkGate and hands its details to the next modules. That way a later step knows exactly who it is dealing with, and can reuse the stored name or number.

When to use it
before Edit a Contact or Remove a Contact, or to personalize a message with stored details.
Watch out
it retrieves one contact; plan a filter for the case where nobody matches.
BulkGate8

Import Contacts

ActionIn the docs only

Many people land in BulkGate in one go, which suits a list exported from an event, a spreadsheet or an older tool. It saves you from adding them one by one by hand.

When to use it
when a spreadsheet of trade-show leads needs to join your SMS audience in a single step.
Watch out
clean the phone numbers in Make first; a messy column produces a messy address book.
BulkGate9

Is Number Blacklisted

ActionIn the docs only

Before anything leaves, the scenario asks BulkGate whether a number sits on your blacklist and gets an answer it can filter on. That protects people who opted out from a stray campaign.

When to use it
just ahead of any marketing send built from another app's list.
Watch out
the module only answers; add a filter after it, otherwise the next module sends anyway.
BulkGate10

Make an Api Call

ActionIn the docs only

Anything in the BulkGate API that the ready-made modules skip becomes reachable here, with the connection you already set up. No second login, no separate key to manage.

When to use it
when you need a BulkGate feature that appears in its API documentation but not in this module list.
Watch out
you write the request yourself, so keep the BulkGate API documentation open while you fill it.
BulkGate11

Remove a Blacklisted Number

ActionIn the docs only

A number comes off your blacklist and can receive your messages again. The typical reason is a customer who opted back in, and the scenario records that choice without anyone editing BulkGate.

When to use it
when someone ticks the marketing consent box again in your CRM or signup form.
Watch out
only trigger it on an explicit new consent, never on a simple profile update.
BulkGate12

Remove a Contact

ActionIn the docs only

A contact disappears from your BulkGate address book, which keeps the list aligned with people who closed their account or asked to be forgotten.

When to use it
when a deletion request is logged in your support tool or your customer database.
Watch out
a deletion cannot be undone from the scenario; test it on a dummy contact with Run once before switching the scenario on.
BulkGate13

Remove a Shortened URL

ActionIn the docs only

A short link created through BulkGate is deleted, so an expired offer stops sending people to a page that no longer makes sense.

When to use it
once a promotion ends and its landing page goes offline, as the last step of the campaign's clean-up scenario.
Watch out
messages already delivered still contain the link, and after removal it leads nowhere; Edit Shortened URL is the softer option.
BulkGate14

Resend an OTP

ActionIn the docs only

Someone who never received their one-time code gets it again without starting the whole verification over. That rescues sign-ups that would otherwise stall at the code screen.

When to use it
when your app reports a click on "send the code again" and calls the scenario.
Watch out
it continues an OTP started with one of the Send an OTP modules; map the reference from that first send.
BulkGate15

Send a Marketing (Bulk) SMS (Different Text)

ActionIn the docs only

A campaign reaches many recipients at once, with a text that changes for each of them: first name, order, store. Personal enough to read like a message, sent in one bulk run.

When to use it
when each customer's message includes their own details pulled from a sheet or a CRM.
Watch out
if every person gets the exact same words, the Same Text version is simpler to set up.
BulkGate16

Send a Marketing (Bulk) SMS (Same Text)

ActionIn the docs only

One identical text goes to a whole list of numbers in a single send, the quickest way to announce a sale, an opening or a change of hours.

When to use it
for a broadcast where nothing in the wording depends on who reads it.
Watch out
run Is Number Blacklisted on the list first, and check your credit with Check Credit Balance before a large send.
BulkGate17

Send a Notification SMS Message

ActionIn the docs only

A single transactional text reaches one person when an event concerns them: order shipped, appointment confirmed, ticket answered. It is the module most first scenarios start with.

When to use it
whenever the message is triggered by something that customer did, not by a campaign.
Watch out
keep promotions out of it and use the marketing modules for those, so the two kinds of traffic stay separate.
BulkGate18

Send a Notification Viber Message

ActionIn the docs only

The same kind of one-to-one notification lands in Viber instead of the SMS inbox. For customers who live in that app, the message sits next to their chats rather than among promo texts.

When to use it
in markets or customer bases where Viber is the usual channel, for delivery updates or booking reminders.
Watch out
to fall back to SMS, first confirm with Run once that Watch Delivery Reports returns reports for Viber sends too.
BulkGate19

Send a Viber Marketing (Bulk) Message (Different Text)

ActionIn the docs only

A Viber campaign goes out to a list, and every recipient reads a text built from their own data. Loyalty points, last purchase or local store can change from one person to the next.

When to use it
for a personalized Viber offer driven by fields from your CRM or a spreadsheet.
Watch out
map the personal fields carefully during Run once; an empty field shows as a gap in a message people will read.
BulkGate20

Send a Viber Marketing (Bulk) Message (Same Text)

ActionIn the docs only

Everyone on the list receives one shared Viber message in a single campaign. It suits announcements where personalization adds nothing and speed of setup matters more.

When to use it
for a store opening, a new collection or a service notice aimed at your whole Viber audience.
Watch out
run Is Number Blacklisted on the list first, exactly as you would before an SMS campaign.
BulkGate21

Send an OTP via SMS

ActionIn the docs only

A one-time password reaches the user by text message, which gives your signup or checkout a second check without building an SMS gateway yourself.

When to use it
when your app calls the scenario at login or at a sensitive step, such as changing a payout account.
Watch out
sending is half the job; the scenario still needs Verify an OTP to confirm what the user typed.
BulkGate22

Send an OTP via Viber

ActionIn the docs only

The verification code arrives in Viber rather than by SMS. Users who keep Viber open all day see it at once, next to their conversations.

When to use it
for audiences who mostly use Viber, or as a second channel your app offers on the code screen.
Watch out
keep Send an OTP via SMS as a fallback in the same flow for users without the app.
BulkGate23

Shorten an URL

ActionIn the docs only

A long tracking link becomes a short one that fits in an SMS without eating half the characters. Your message stays readable and the link stays clickable.

When to use it
just before a send module, then map the short link into the message text.
Watch out
save what it returns in a sheet; Edit Shortened URL and Remove a Shortened URL need it later.
BulkGate24

Verify an OTP

ActionIn the docs only

The code a user typed is checked against the one BulkGate sent, and the scenario gets a yes or no it can route on. That closes the loop started by a Send an OTP module.

When to use it
when your login or checkout page sends the typed code to Make.
Watch out
add a router after it, one path for a valid code and one for a wrong or expired attempt.
Need help

Need help automating BulkGate with Make?

A person reads every message.

FAQ

BulkGate and Make: frequent questions

01Is the BulkGate Make integration free?
Yes on the Make side: BulkGate is a standard app, available from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Every module run counts as one operation on your plan. Paid Make plans lower the interval to 1 minute and remove the cap on active scenarios. BulkGate itself needs its own active account, and its pricing is set by BulkGate, not by Make.
02What do you need to connect BulkGate to Make?
An active BulkGate account and API credentials created in it. In BulkGate, go to Modules and APIs, open the API you want and click Create API, then copy the Client ID and the API token shown on screen. In Make, add any BulkGate module, click Create a connection, optionally give it a name and paste both values. The documentation also calls the ID an Application ID; it is the same credential.
03Do BulkGate triggers in Make fire instantly?
No. Both triggers, Watch Delivery Reports and Watch Bulk Delivery Reports, are scheduled: Make checks BulkGate on the scenario's schedule instead of receiving a webhook. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that; paid plans go down to 1 minute. For sends, the start usually comes from another app anyway, such as a form or a shop, which calls or feeds the scenario before a BulkGate module sends the message.
04What if a BulkGate module you need is missing in Make?
Use Make an Api Call. It reaches any endpoint of the BulkGate API with the connection you already created, so a feature missing from the 24 actions and 2 triggers is still within reach. You write the request yourself, based on BulkGate's own API documentation. Also keep in mind that the page Make publishes for this app is labeled as AI-generated content, so confirm important behavior with BulkGate before building a critical flow on it.
05Make or n8n for BulkGate?
It depends on the tool your team already uses and knows. On Make, BulkGate offers 26 ready-made modules covering SMS, Viber, one-time codes, contacts, blacklist and short links, plus Make an Api Call for the rest. n8n may also offer a BulkGate node, so compare the list of actions on each side against what your scenario needs. Pick the platform where your other automations already live, which keeps connections and monitoring in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations