Resources · Make integration

SMSINDIAHUB Make integrationAutomate SMSINDIAHUB with Make.

Need a text message to go out the moment something happens in another tool? The SMSINDIAHUB Make integration gives you 2 action modules, one to send an SMS and one to call the API. This guide is for teams new to Make: link your account, then build and test a first scenario.

Try the SMSINDIAHUB integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SMSINDIAHUB Make integration do for you?

The SMSINDIAHUB Make integration lets a Make scenario (the automation you build, a chain of steps) send an SMS through your SMSINDIAHUB account. Something happens in another app, Make picks it up, and the text goes out without anyone copying a phone number by hand.

A confirmation text after an order. An online store records a sale in its shop app, and the next step in the scenario is Send an SMS, so the buyer hears back without a staff member typing anything.

A quick reply to a new lead. A form tool receives a request, Make passes the details along, and SMSINDIAHUB sends a short acknowledgment. Your sales team starts the conversation already warm.

Anything the two modules skip. Make an API Call reaches any endpoint of the SMSINDIAHUB API with the same connection, which is the way out when a feature has no ready-made module.

Be aware that the official Make documentation for SMSINDIAHUB is thin: Make itself says public information about this app is limited. Expect to test each step with Run once rather than rely on a detailed guide. If you are still weighing platforms, the n8n vs Make comparison and the Make review lay out the differences, and Make troubleshooting helps when a run fails.

Connect

How do you connect SMSINDIAHUB to Make?

  1. 01

    Add an SMSINDIAHUB module

    In your scenario, click the + and search for SMSINDIAHUB. Pick Send an SMS, then click Create a connection. A connection is your SMSINDIAHUB account linked to Make once and reused by every module of the app.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, handy when several accounts sit side by side. Then authorize Make on the SMSINDIAHUB page, or paste the key SMSINDIAHUB gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. The connection now appears in the module's drop-down, and the second module, Make an API Call, can use it too without asking for your credentials again.

First scenario

Build your first scenario with SMSINDIAHUB

GoalWhen a new record lands in another app, Make sends an SMS through SMSINDIAHUB.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. SMSINDIAHUB has no trigger, so this first module comes from the app where the event starts.

  2. 02

    Pick the starting app

    Search for that app, choose its module and link it with Create a connection. Fill its fields: once connected, Make lists the folders, sheets or objects it can read.

  3. 03

    Add Send an SMS

    Click the + on the right of the first module, search for SMSINDIAHUB and pick Send an SMS. Map the data coming from the previous module into the fields Make shows.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received (a bundle is one item passed along, here one record). Check that the text reached the phone.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule, every 15 minutes by default, then switch the scenario on. From there, each new record in the starting app triggers a text.

Modules

What the SMSINDIAHUB modules do

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

SMSINDIAHUB1

Make an API Call

ActionIn the docs only

Reach any endpoint of the SMSINDIAHUB API straight from your scenario, reusing the connection you already created. You get access to features that have no dedicated module.

When to use it
a task your account supports goes beyond sending a single text and Send an SMS cannot do it.
Watch out
Make gives no detail on the endpoints, so you need the API documentation from SMSINDIAHUB, if it publishes one.
SMSINDIAHUB2

Send an SMS

ActionIn the docs only

Get a text message out to a phone through your SMSINDIAHUB account, filled with data from earlier steps of the scenario. This is the module most scenarios with this app end on.

When to use it
a customer should hear back as soon as an order, a booking or a form lands in another app.
Watch out
each run counts one operation per bundle, so a step that returns many records sends many texts.
Need help

Need help automating SMSINDIAHUB with Make?

A person reads every message.

FAQ

Questions about SMSINDIAHUB and Make

01Is the SMSINDIAHUB Make integration free?
Yes, on the Make side. SMSINDIAHUB is a standard app, available from the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes of execution at most and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one module run on one bundle. Standard apps like this one work on every plan, so nothing changes if you upgrade later.
02What do you need to connect SMSINDIAHUB to Make?
An active SMSINDIAHUB account and a Make account. The Make documentation lists no other prerequisite and gives no official connection steps, so the generic Make flow applies. Add an SMSINDIAHUB module, click Create a connection, name it if you want, then either authorize Make on the SMSINDIAHUB page or paste the key the app gives you, and click Save. That one connection then serves both modules, Send an SMS and Make an API Call, so you only enter your credentials once.
03Can SMSINDIAHUB start a Make scenario on its own?
No. SMSINDIAHUB has no trigger module in Make, only 2 actions. A scenario that sends texts therefore starts elsewhere. The usual route is the trigger of another app, such as a form tool or a store, placed as the first module. The other route is the schedule on the first module: a new scenario runs every 15 minutes by default, and paid plans can go down to 1 minute. In both cases SMSINDIAHUB acts at the end of the chain, when the scenario hands it the data.
04What if the SMSINDIAHUB module you need is missing in Make?
Use Make an API Call. That module can reach any endpoint of the SMSINDIAHUB API from your scenario, with the same connection as Send an SMS. It covers whatever the listed modules leave out. Keep in mind that Make flags the documentation for this app as limited, because little public information exists about SMSINDIAHUB. If SMSINDIAHUB publishes an API reference, keep it open while you set up the call, then test it with Run once and read the bundle Make returns before switching the scenario on.
05Should you use Make or n8n for SMSINDIAHUB?
It depends on where the rest of your automations already live. In Make, SMSINDIAHUB offers 2 modules, Send an SMS and Make an API Call, and it works from the Free plan. The same app often has an n8n node as well, so check whether it exists before you choose. Neither tool is ranked here. A useful test: build the SMS step in Make, run it once, and see whether the scenario editor suits the way your team works. If it does, there is little reason to split your automations across two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations