Resources · Make integration

kwtSMS Make integrationAutomate kwtSMS with Make.

Need a text message to go out the moment something happens in another tool? The kwtSMS Make integration gives you 3 action modules: send an SMS, read your balance, list your sender IDs. This page walks you through the connection and a first working scenario.

Try the kwtSMS integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the kwtSMS Make integration do for you?

It lets Make send text messages through your own kwtSMS account, with no code. You build a scenario (the automation itself, a chain of modules) where another app supplies the event and the data, and a kwtSMS module (one brick of that chain) sends the SMS or reads your account details.

Confirm a booking by text. A clinic or a salon collects appointments through an online form. The form app starts the scenario, and Send SMS texts the customer a confirmation using the name and time from the form.

Keep an eye on credit. Place Get Balance right after Send SMS, and every run shows how much credit the account still holds. When you click Run once, you read that value in the bundle (one item passed from a module to the next).

Pick the right sender. Get SenderIDs returns the sender IDs attached to your account, which helps when several brands or branches share one kwtSMS login.

Know the limits before you start. kwtSMS has no trigger, so it never starts a scenario by itself, and it has no generic API call module either: the three modules are all you get. The kwtSMS documentation on Make also warns that it is AI-generated, so double-check any detail that matters with kwtSMS. Want the bigger picture first? Read our Make review, compare costs on Make pricing, or weigh the options in n8n vs Make.

Connect

How do you connect kwtSMS to Make?

  1. 01

    Request API access in kwtSMS

    Log in to kwtSMS and click Request API access in the menu. Fill out the form completely and accurately, then submit it. kwtSMS reviews the request before your Basic Auth credentials become available.

  2. 02

    Create the connection in Make

    In your scenario, add any kwtSMS module and click Create a connection. A connection is your kwtSMS account linked to Make once, then reused by every kwtSMS module. The Connection name field is optional.

  3. 03

    Paste your credentials

    Enter the credentials you copied from your kwtSMS account, or follow the instructions shown on screen, and save. From now on, each kwtSMS module in any scenario can pick this connection from the list.

First scenario

Your first scenario: text a customer after a form

GoalWhen someone submits your booking form, Make sends them an SMS through kwtSMS and then reads your remaining balance.

  1. 01

    Start a new scenario

    Open the Scenarios page, create a new scenario and click the +. Add the trigger of your form app first: kwtSMS has no trigger, so another app has to start things.

  2. 02

    Add Send SMS

    Click the + to the right of the form module, search for kwtSMS and choose Send SMS. Select your connection, or click Create a connection if this is your first kwtSMS module.

  3. 03

    Map the form data

    Fill the fields of Send SMS by dragging in data from the form module, such as the phone number and the customer name the form collected. Each submission becomes one bundle, so each person gets a text of their own.

  4. 04

    Read the balance

    Add Get Balance after Send SMS. Its name says what it does: it reports the credit left on your kwtSMS account after the text goes out.

  5. 05

    Test, then switch it on

    Submit a test entry to your form with your own number, then click Run once and check the bundles of each module. When the text arrives, set the schedule on the first module and switch the scenario on.

Modules

What each kwtSMS module does

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

kwtSMS1

Get Balance

ActionIn the docs only

Tells you how much credit is left on your kwtSMS account, so a scenario can report it without anyone logging in to check. Each call costs one operation, the unit Make counts on your plan.

When to use it
right after Send SMS in a scenario that sends many texts, so the run history shows the balance falling.
Watch out
it only reads the balance, it never tops the account up.
kwtSMS2

Get SenderIDs

ActionIn the docs only

Returns the sender IDs registered on your kwtSMS account, the names your recipients see as the sender. Handy for checking what the account can actually use before you configure a send.

When to use it
when one kwtSMS login serves several shops or brands and you want to confirm which sender IDs exist.
Watch out
it lists what already exists, it does not register a new sender ID.
kwtSMS3

Send SMS

ActionIn the docs only

Sends a text message from your kwtSMS account using data that earlier modules brought in, such as a phone number from a form or a CRM. This is the module that does the real work of the integration.

When to use it
a booking confirmation, a delivery notice or a reminder triggered by an event in another app.
Watch out
it runs once per bundle, so a list of contacts means one text and one operation for each person on it.
Need help

Need help automating kwtSMS with Make?

A person reads every message.

FAQ

kwtSMS and Make: common questions

01Is the kwtSMS Make integration free?
Yes on the Make side: kwtSMS is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs and 5 minutes of execution per run. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and count usage in credits each month. Sending texts is a separate matter: you need an active kwtSMS account, and kwtSMS sets its own subscription terms on its pricing page, which this page does not cover.
02What do you need to connect kwtSMS to Make?
You need an active kwtSMS account and API access. Inside kwtSMS, click Request API access, complete the form accurately and submit it for review. Once kwtSMS approves it, you get Basic Auth credentials. Back in Make, add a kwtSMS module, click Create a connection, name it if you like, and paste those credentials. The same connection then serves all three kwtSMS modules, in every scenario you build. Without those credentials, the connection has nothing to work with.
03Can kwtSMS start a Make scenario in real time?
No, kwtSMS has no trigger module, so it cannot start a scenario at all. The scenario has to begin with something else. The usual choice is the trigger of another app, a form, a shop or a CRM, followed by Send SMS. If that other app offers an instant trigger, meaning it calls Make through a webhook as soon as something happens, the text goes out right away. Otherwise Make checks on the schedule you set, every 15 minutes by default.
04What if the kwtSMS module you need is missing in Make?
It depends on what you are after. kwtSMS on Make offers exactly three modules: Send SMS, Get Balance and Get SenderIDs, and there is no Make an API Call module to reach other parts of the kwtSMS API. If you need something beyond those three, look for another SMS app in Make that covers the feature, or ask the team for help designing a workaround. Also keep in mind that the kwtSMS documentation on Make is flagged as AI-generated.
05Should you use Make or n8n with kwtSMS?
It depends on the tool your team already works in. Apps on Make often have an equivalent node in n8n, but this page cannot confirm one exists for kwtSMS, so check the n8n node list before choosing. If you go with Make, the facts here hold: three action modules, no trigger, a connection through Basic Auth credentials. Pick the platform your team knows, and compare both on your own real scenario rather than on general claims.
Same platform

Other docs you might need on this stack.

Browse all integrations