SMS integrations: connect GoHighLevel, Zapier, Make, n8n and more to your own phone
Every tool that can send an HTTP request can send SMS through textbee, and every tool that accepts a webhook can receive them. The pages below use only what each tool ships today: its HTTP action, its webhook trigger and the textbee API. Each one has the exact field values, a prompt you can hand to an AI agent, the automations that work well, and the limits of that route.
Updated
- GoHighLevelSend SMS from GoHighLevel workflows through textbee with the Custom Webhook action, and start GHL workflows from incoming texts with the Inbound Webhook trigger. Field values, the JSON body, an agent prompt, what it costs on the GHL side and the limits of the webhook route.Updated September 25, 2026
- ZapierSend SMS from any Zap through textbee with a Webhooks by Zapier Custom Request, and trigger Zaps from incoming texts with Catch Hook. The field values, the JSON body, an agent prompt, the plan requirement and the limits.Updated September 25, 2026
- MakeSend SMS from a Make scenario through textbee with the HTTP Make a request module, and start scenarios from incoming texts with a Custom webhook. Module settings, the JSON body, an agent prompt, what the Free plan covers and the limits.Updated September 25, 2026
- n8nSend SMS from n8n through textbee with the HTTP Request node and a Header Auth credential, and trigger workflows from incoming texts with the Webhook node. Node settings, the JSON body, signature verification, an agent prompt and limits. Works self-hosted.Updated September 25, 2026
- Google SheetsText every number in a Google Sheet through textbee: a short Apps Script calls the send endpoint from a custom menu or a time trigger, marks each row as sent, and keeps the API key in script properties. Includes an agent prompt, the quotas and how replies get back into a sheet.Updated September 25, 2026
- Home AssistantSend SMS from Home Assistant automations through textbee with a rest_command, and run automations from incoming texts with a webhook trigger. The YAML, the secrets entry, an agent prompt, and what has to be reachable from the internet.Updated September 25, 2026
- Node-REDSend SMS from a Node-RED flow through textbee with a function node and an http request node, and receive texts with an http in node that verifies the signature. Node settings, the function code, an agent prompt and limits. Core nodes only.Updated September 25, 2026
- SlackPost incoming SMS into Slack with Workflow Builder: a webhook trigger receives the textbee webhook and a Send a message step posts the sender and the text to a channel, with nothing to host. Plus how to send SMS from Slack through Make, Zapier, n8n or a bot.Updated September 25, 2026
- ShopifyText Shopify customers when an order is placed, paid or shipped, through textbee: a Shopify Flow workflow calls the send endpoint with the Send HTTP request action, or Zapier, Make and n8n do it on any plan. Includes the Liquid body, an agent prompt, what Shopify sends by itself, and how replies get back to the order.Updated September 30, 2026
- WooCommerceText WooCommerce customers when an order is confirmed, on hold, shipped or cancelled, through textbee: one PHP snippet in the Code Snippets plugin hooks the order status change and calls the send endpoint. Includes the snippet, a reply receiver that adds an order note, an agent prompt and the limits.Updated September 30, 2026
How every integration works
- The tool sends an HTTP POST to
https://api.textbee.dev/api/v1/gateway/send-smswith your API key in the x-api-key header and a JSON body: recipients as an array of E.164 numbers, and message. The phone sends the text within seconds. - For replies, the tool gives you a webhook URL. You register it in the textbee dashboard for the MESSAGE_RECEIVED event, and every text the phone receives arrives there as flat JSON with sender, message and receivedAt.
- Delivery status comes back through the same webhook system (MESSAGE_SENT, MESSAGE_DELIVERED, MESSAGE_FAILED) or by reading the messages endpoint with the smsBatchId the send returned.
One phone sends roughly 10 to 15 messages a minute, and it sends text only. Every page states what its tool charges for the HTTP or webhook feature, with the source and the date.
AI agents
Claude, Cursor and any MCP client send and read SMS through the textbee MCP server, with no HTTP setup at all. For an agent that writes the integration for you, every page below carries a prompt with the API facts and the tool specifics, ready to paste.
A tool that is not listed
If it can send an HTTP request with a header and a JSON body, it can send SMS: the agent quickstart has the two endpoints and the SMS API by language pages have the call in code. If it can receive a webhook, it can receive texts: the webhooks documentation has the payload and the signature check. A tool that can only send flat key-value bodies cannot pass recipients as an array; put Make, Zapier or n8n in between. For a build you would rather not do yourself, the team offers integration help.
Frequently asked questions
Do I have to carry the phone around to use this?
No. The phone that runs textbee stays plugged in at the office or at home. Your tool sends through the API and replies arrive through the webhook, so nobody touches the phone after setup. You never unlock it to send.
What happens when the phone goes offline in the middle of a workflow?
Sends wait in the textbee queue and go out when the phone reconnects, in order. Texts the phone receives while offline are uploaded when it reconnects and reach your tool as a backlog of webhook deliveries. Texts received more than 48 hours before the upload are stored but not sent to webhooks.
Can I use my existing business number, or do I need a new SIM?
Either. Many teams move the business SIM into a spare Android phone and keep the number their customers know. If that SIM is also a personal line, a cheap second SIM dedicated to automation keeps the two apart.
Does the phone need a permanent internet connection?
Yes, Wi-Fi or mobile data, so it can fetch sends from the queue and upload the texts it receives. The SIM only needs normal cellular coverage to send and receive SMS.
Can I run several phones or numbers?
Yes. Register each phone in the same textbee account. The send call picks the default phone unless the body carries a deviceId, so your tool can choose the number per message. Each phone adds roughly 10 to 15 messages a minute.
Can I text international contacts?
Anywhere the SIM can reach. The cost per international text is whatever the carrier plan charges for it, and the recipient sees the same mobile number.
How do I handle STOP and opt-out replies?
Catch the reply with the receive flow, check whether message is STOP or UNSUBSCRIBE, and let your tool tag the contact and remove them from future sends. Consent before the first message and a working opt-out are what keep any SMS channel compliant.
Do long messages get split?
A text over 160 characters (70 with emoji or non-Latin characters) is sent as several segments that the recipient sees as one message. Each segment counts toward the plan allowance.