textbee Logotextbee.dev
Save 44% with yearly billing.View Plans

Automation

Make (formerly Integromat) SMS integration: send and receive texts with the HTTP module

Published and updated

Make connects to textbee with two built-in modules. HTTP, Make a request posts to the textbee send endpoint and sends a text from your Android phone. Webhooks, Custom webhook gives you a URL that textbee posts every incoming text to, so a reply can start a scenario. Both are core Make apps, and the Free plan is enough to try them.

Send
HTTP POST
to the textbee send endpoint
Receive
Webhook
MESSAGE_RECEIVED, flat JSON
Pace
10 to 15 / min
per Android phone
textbee code
None
uses what the tool ships today

What you need

  • A Make account. The HTTP and Webhooks modules are core Make apps.
  • A textbee account with the Android app installed on the phone that holds the SIM, and an API key from the dashboard.
  • A trigger for the send scenario: a form, a sheet, a CRM module, a schedule, or a webhook from another tool.
  • The textbee app on the phone. Download the app, then create an API key in the dashboard.

Send SMS from Make

The HTTP module has to send a raw JSON body. The form-style body types turn recipients into a string, which textbee rejects.

  1. Add the HTTP module

    In the scenario click the plus sign and choose HTTP, then Make a request.

  2. Configure the request

    Map the phone number and the message from the earlier module into the request content. Keep the square brackets around the number.

    FieldValue
    URLhttps://api.textbee.dev/api/v1/gateway/send-sms
    MethodPOST
    HeadersAdd item: x-api-key = YOUR_TEXTBEE_API_KEY
    Body typeRaw
    Content typeJSON (application/json)
    Parse responseYes
    JSON
    {
      "recipients": ["{{1.phone}}"],
      "message": "Hi {{1.name}}, your order {{1.orderId}} has shipped."
    }
  3. Run once

    Click Run once and fire the trigger. The module output shows data.success true and data.smsBatchId. The text arrives on the test number within a minute.

  4. Schedule the scenario

    Turn the scenario on. An instant trigger such as a webhook runs at once; a polling trigger runs on the interval you set.

Receive SMS in Make

Make hosts the webhook URL, so nothing on your side needs a public address. textbee posts to it and Make reads the flat JSON into fields.

  1. Create a Custom webhook

    Start a scenario with Webhooks, Custom webhook. Click Add, give it a name, save it and copy the URL.

  2. Register it in textbee

    In the textbee dashboard open Webhooks, create one with the Make URL, select MESSAGE_RECEIVED and set a signing secret.

  3. Determine the data structure

    While the webhook waits for data, text the phone from another number. Make reads the JSON and creates fields for sender, message, receivedAt and the rest.

  4. Add the next modules

    Map sender and message into a Google Sheets row, a CRM contact, a Slack message, or a second HTTP module that replies.

Ask your AI agent to set it up

The prompt below carries the endpoints, the payloads and the Make details from this page. Change the line that starts with What I want, paste the prompt into your agent, and it walks you through the setup with your own field names and numbers.

Prompt for your AI agent

Paste it into Claude, ChatGPT, Cursor or any coding agent. It carries the textbee API facts and the Make details the agent needs, so it does not guess.

I want to connect textbee to Make. textbee is an SMS gateway that sends and receives SMS through my own Android phone. Help me set it up step by step.

Facts about the textbee API. Use only these. Do not invent endpoints or fields.
- Send an SMS: POST https://api.textbee.dev/api/v1/gateway/send-sms with the header x-api-key: <TEXTBEE_API_KEY> and a JSON body like {"recipients": ["+12015550123"], "message": "Hello"}. recipients must be a JSON array of E.164 numbers, even for one number. Optional fields: deviceId, simSubscriptionId, scheduledAt (ISO 8601, in the future). The response is {"data": {"success": true, "smsBatchId": "..."}}.
- Check delivery or read replies: GET https://api.textbee.dev/api/v1/gateway/messages with the same header. Filters: direction=received, smsBatchId=<id from the send>, from and to as ISO timestamps. Each row has a status such as sent, delivered, failed or received.
- Receive an SMS: textbee posts JSON to a webhook URL I register in the dashboard. A MESSAGE_RECEIVED delivery has these top-level fields: smsId, message, deviceId, webhookSubscriptionId, webhookEvent, idempotencyKey, sender, receivedAt. The header X-Signature holds an HMAC-SHA256 hex digest of the raw body, keyed with the signing secret I set on the webhook. Retries reuse the same idempotencyKey.
- Limits: One Android phone sends roughly 10 to 15 messages a minute. Text only, no MMS. Messages over 160 characters are split into segments.

What I want: Send SMS from a Make scenario, and start a scenario from every text my phone receives.

Make specifics you should know:
- The HTTP, Make a request module needs Body type Raw and Content type JSON (application/json) to send a JSON array. Mapped values use the {{1.field}} form.
- Webhooks, Custom webhook exposes top-level JSON keys as fields once the first request determines the data structure.
- Make cannot verify an HMAC header with its standard modules alone; keep the webhook URL private.
- The Free plan includes 1,000 credits a month and 2 active scenarios; every module run uses credits.

Give me:
1. The exact clicks and field values in Make, using its real field labels.
2. The request body or field mapping, with placeholders for my API key and phone numbers. Never ask me to paste the real key into this chat.
3. A test with one number and what a correct result looks like.
4. The three most likely failure causes and how to check each one.

Automations that work well

Order shipped
Shopify or WooCommerce trigger on a fulfilled order, then an HTTP module that texts the customer the tracking link.
Reminders from a sheet
A schedule trigger, a Google Sheets Search Rows module for tomorrow, an Iterator, then one HTTP request per row.
Reply capture
Custom webhook, then a Google Sheets Add a Row module with sender, message and receivedAt.
Keyword autoresponder
Custom webhook, a Router with a filter on message, then an HTTP module that replies to sender with the matching answer.

What works and what does not

Works today

  • Sending from any Make trigger, with mapped fields in the text
  • Incoming texts as an instant trigger, with sender and message as fields
  • Routers and filters that branch on the message text
  • Delivery checks with an HTTP module that GETs the messages endpoint by smsBatchId

Not with this route

  • Sending recipients through a form-style body type
  • Signature verification; keep the webhook URL private
  • MMS

What Make charges

The HTTP and Webhooks apps carry no plan restriction in the Make documentation. The Free plan includes 1,000 credits a month and 2 active scenarios, and every module run uses credits. make.com, checked on September 25, 2026. textbee itself charges a flat monthly plan with messages included; see pricing.

Frequently asked questions

Is there a textbee app in Make?

No. The HTTP and Webhooks modules do the job without an app, and the Make documentation lists no plan restriction for them.

Which body type do I pick?

Raw, with the content type set to JSON (application/json). The form types send recipients as a string and textbee answers 400 Invalid recipients.

How do I send to many numbers?

Put every number in the recipients array, up to the per-batch limit of your plan, or use an Iterator to send one request per row. The phone sends roughly 10 to 15 messages a minute either way.

Does the webhook need a public address?

No. Make hosts the URL on its own domain. textbee posts there, and nothing on your side has to be reachable.

Can Make check delivery?

Yes. Add a Sleep of a minute, then an HTTP module that GETs the messages endpoint with smsBatchId set to the value from the send. Each row has a status such as sent, delivered or failed.

Sources

  1. make.com, checked on September 25, 2026
  2. apps.make.com: HTTP app, checked on September 25, 2026
  3. help.make.com: Webhooks, checked on September 25, 2026

Read next