Resources · Make integration

Thaibulksms OTP Make integrationAutomate Thaibulksms OTP with Make.

Need to send a one-time code by SMS and check it without writing code? The Thaibulksms OTP Make integration gives you 3 action modules: one sends the code, one verifies it, one calls the API directly. This page shows how to link your account and build a first scenario.

Try the Thaibulksms OTP integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Thaibulksms OTP Make integration do for you?

The Thaibulksms OTP Make integration lets a Make scenario, the automation you build as a chain of modules, send a one-time SMS code through Thaibulksms and then check the code a person types back. Each module is one brick of that chain, and all three here are actions.

A sign-up that proves the phone is real. When another app hands Make a new registration, Send an SMS OTP fires the code, and Verify an SMS OTP confirms it later in the flow before you mark the contact as checked.

A second check before a sensitive step. An operations team can place the pair in front of an approval, so the request only moves on once the code matches. The same pattern fits a booking or a payment confirmation you already run in another tool.

A call the listed modules do not cover. Make an API Call reaches any endpoint of the Thaibulksms OTP API with the connection you already set up, which is handy when you need something beyond sending and checking.

Know the limits before you start. The app has no trigger, so your scenario has to begin with another app or with Make's own schedule. Make's documentation for this app is also thin: it says there is not enough public information to describe it fully, so expect to read the fields in the editor rather than in a guide. The Make review gives a wider view of the platform, and if the same app interests you on n8n, the n8n vs Make page lays out how the two tools differ.

Connect

How do you connect Thaibulksms OTP to Make?

  1. 01

    Add a Thaibulksms OTP module

    In your scenario, add any of the three modules, then click Create a connection. A connection is your Thaibulksms account linked to Make once, and every module of the app reuses it afterwards.

  2. 02

    Name it and authorize

    Give the connection a name if you like, it helps when you run several accounts. Then either authorize Make on the Thaibulksms page that opens, or paste the key your Thaibulksms account gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. Back in the module, the fields should now load, which is the sign the link works. If they stay empty, open the connection again and check the key or the authorization.

First scenario

Your first scenario with Thaibulksms OTP

GoalWhen a new sign-up arrives from another app, Make sends a code with Thaibulksms OTP and then verifies the code the person returns.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Thaibulksms OTP has no trigger, start with the app that collects your sign-ups.

  2. 02

    Add Send an SMS OTP

    Click the + to the right of that first module, search Thaibulksms OTP, pick Send an SMS OTP and create the connection. Map the data from the previous module into its fields.

  3. 03

    Add Verify an SMS OTP

    Click the + again and add Verify an SMS OTP. It needs the code the person typed, which only exists once they reply. Map that code from the step that collects it, along with what the send step returned. In practice, this check often sits in a second scenario that starts when the reply comes in.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module and read the bundles it received, a bundle being one item passed from one module to the next.

  5. 05

    Schedule and switch on

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

Modules

What each Thaibulksms OTP module does

Thaibulksms OTP gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Thaibulksms OTP1

Make an API Call

ActionIn the docs only

You get a direct line to the Thaibulksms OTP API, using the connection you already created, so any endpoint the three listed modules skip is still within reach of your scenario.

When to use it
pick it only when neither Send an SMS OTP nor Verify an SMS OTP does the job you need.
Watch out
with thin official documentation, you will have to read the Thaibulksms API reference yourself to build the request.
Thaibulksms OTP2

Send an SMS OTP

ActionIn the docs only

This module gives your scenario a way to text a one-time code through Thaibulksms, the first half of any phone check you build in Make.

When to use it
right after the step that brings in a new sign-up, an order or a request that needs the person to prove they own the number.
Watch out
keep what this module returns and map it into the verify step, since the check needs to match the code that was actually sent.
Thaibulksms OTP3

Verify an SMS OTP

ActionIn the docs only

Here you find out whether the code a person typed matches the one Thaibulksms sent, so the rest of your scenario can act on a confirmed answer instead of a guess.

When to use it
after Send an SMS OTP, once your form or app has collected the code the person entered.
Watch out
the code arrives after the SMS, so this step usually belongs to the scenario that starts when the person submits it.
Need help

Need help automating Thaibulksms OTP with Make?

A person reads every message.

FAQ

Questions people ask about Thaibulksms OTP and Make

01Is the Thaibulksms OTP Make integration free?
Yes, Thaibulksms OTP is a standard app, so it works on Make's Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and lift the scenario cap. Any cost on the Thaibulksms side is separate and not covered here, and Make counts each module run as one operation against your monthly credits.
02What do you need to connect Thaibulksms OTP to Make?
A Thaibulksms account and a Make account. Make's documentation lists no specific prerequisite for this app. You add a module, click Create a connection, optionally name it, then authorize Make on the Thaibulksms page or paste the key your account provides, and click Save. The documentation is limited for this app, so keep your Thaibulksms dashboard open to find the credential the connection window asks for. Once saved, the same connection serves all three modules, so you only do this once per account.
03Does Thaibulksms OTP trigger Make scenarios in real time?
No, because the app has no trigger module at all. Your scenario starts another way: with a trigger from another app, such as the form or tool that collects sign-ups, or with Make's own schedule on the first module, every 15 minutes by default on a new scenario. Once started, the scenario runs the Thaibulksms OTP modules in the order you placed them. The Thaibulksms modules themselves never start a run; they only act when an earlier module passes them a bundle.
04What if the Thaibulksms OTP module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Thaibulksms OTP API with the same connection, which covers what Send an SMS OTP and Verify an SMS OTP do not. Keep in mind that Make's own documentation for this app is limited because little public information exists, so you will rely on the Thaibulksms API reference to shape the request and read the response. Try the call with Run once first and read the bundle it returns before switching the scenario on.
05Should you use Make or n8n for Thaibulksms OTP?
It depends on the tool your team already runs. On Make you get the three modules described on this page, a visual editor and a Free plan to test with. The same app often has an n8n node as well, so check whether it exists there before deciding. Compare how each tool fits the rest of your stack and the people who will maintain the scenario, rather than the SMS app alone.
Same platform

Other docs you might need on this stack.

Browse all integrations