Android Texter for Make.com: Modules, Setup and Known Issues
The Make app (Make was Integromat) gives you Android Texter as a set of modules you drop into a scenario. It has the widest surface of our three no-code connectors, including a universal API Call module that reaches any endpoint we have, even ones with no module of their own. We build and maintain it.
Or search for Android Texter in the module picker inside your own Make account.
Authentication
A connection holding your API key, sent as the X-API-Key header. One connection works across every module in the scenario.
What it can do
- New inbound message (instant)Trigger
A signed HTTPS webhook, so the scenario starts within seconds of a text arriving. Use this one for anything time sensitive.
- New inbound message (polling)Trigger
The same event, checked on the scenario's schedule instead. Useful when your Make plan runs scenarios on a timer anyway.
- Send an SMSAction
One recipient, from a phone you pick from a dropdown of your paired devices. Setting Media URL makes it an MMS. Returns the message ID and the device that took it.
- Send a broadcastAction
Up to 500 recipients in one call, personalized per recipient by our server from their contact row: first_name, last_name, full_name, name, company, city, state, birthdate, review_date.
- Create or update a contactAction
Creates on a new number, merges onto the existing row otherwise. Blank fields are not sent, so they never wipe what is already there, and tags are additive.
- Make an API callAction
An authorized call to any Android Texter endpoint, for anything the other modules do not cover. The connection supplies the auth header.
- Get conversation historySearch
One conversation, newest first, with media fields. Pass the thread ID from a trigger event to read a group text.
- Get devicesSearch
Paired phones with online status, number, battery and last seen. Worth a check before a large send.
Setting it up
- Pair the phone you want to text from, in the Android Texter dashboard.
- Create an API key under Dashboard, Settings, API Keys, and copy it. Keys start with atx_ and are shown once.
- In Make, add an Android Texter module, create a connection and paste the key.
- For inbound, choose New inbound message (instant). Make gives you a webhook URL and we register it on your account when you attach it.
Known issues
Things people actually run into with Make, and what to do about each one.
Personalization tokens vanish from a broadcast: everyone gets the literal text with no name, or the token is simply gone.
Make treats anything written as a double-brace token in the Message field as its own mapping and removes it before the call reaches us. Build the token out of string pieces instead, so Make passes it through intact: {{ "{" + "{" + "first_name|there" + "}" + "}" }}. That arrives as the literal token and our server resolves it per recipient, falling back to there when the contact has no first name. The same trick works for any of the personalization fields.
The polling trigger is slow to notice a reply.
It only looks when the scenario runs, so the delay is your schedule interval, not ours. Switch to New inbound message (instant) for a webhook that fires in seconds.
An endpoint you need has no module.
Use Make an API call. It is a full REST module on the same connection, so anything in the API reference is reachable without waiting for us to add a module.
The listing page shows conflicting badges about who maintains the app.
Make's own page renders both a Verified badge and a line saying community maintained. We wrote and maintain this app, and support questions about it come to us at [email protected].
Questions
How many operations does a scenario use?
Make counts one operation per module run. A broadcast to 500 people is one call to us and one Make operation, not 500.
Can I send from several phones?
Yes. Pair more than one phone and leave the device field empty to send from the first online one, or use the broadcast module's device mode to spread the sends across all of them.
Is there a module for reading one message by ID?
Not yet. Use Make an API call against the message status endpoint, or Get conversation history for the whole thread.
Other ways in
- Zapier: our app, live on the zapier marketplace.
- n8n: our community node, on npm.
- Composio: built by composio, not by us.
- MCP server: our own, for AI assistants. The key stays on your machine.
- REST API: every endpoint, with signed webhooks for inbound messages.
Worked setups
- Apollo.io Add SMS to an Apollo sequence without a Twilio account.
- Calendly Custom appointment reminders, without Calendly's Standard plan.
- GoHighLevel Send from GHL for the clients carrier registration turns away.
- LoanPro Payment reminders from LoanPro with no 10DLC paperwork.
- Helcim Text a payment receipt after a Helcim transaction.
- Flowhub Pickup notifications from Flowhub dispensary POS.
Text from your own number
Free for 100 texts a day on one phone. Pro is $10 a month per phone, with no message cap from us.
Get started free