Android Texter for n8n: the Community Node, Setup and Limits
n8n-nodes-android-texter is our community node for n8n, the self-hostable automation tool. It has the deepest operation list of the three, covering messages, conversations, scheduled messages, contacts, devices and spam, and the node can also be handed to n8n's AI Agent as a tool so a model can text on your behalf. Reach for n8n if you self-host, want no per-task pricing, or want an AI step in the middle of the workflow.
In n8n: Settings, Community Nodes, Install, then enter n8n-nodes-android-texter.
Authentication
An Android Texter API credential holding your key, sent as X-API-Key. No OAuth. Saving the credential tests it against the account endpoint.
What it can do
- Message: SendAction
One or several numbers in the To Phone field, up to 1600 characters. Options: Device ID, Media URL to make it an MMS, Scheduled At, and SIM Slot on a dual-SIM phone.
- Message: Send BroadcastAction
Up to 500 numbers, commas or new lines, each getting its own text with personalization filled in per contact.
- Message: Get StatusAction
The status of one send by message ID: queued, sent, failed or cancelled.
- Message: Get HistoryAction
One conversation, newest first, by phone number, with page and limit. Add the thread ref from List Conversations for a group text.
- Message: SearchAction
Sent and received texts containing a word or phrase, one item per message.
- Conversation: ListAction
Most recent first, with a folder filter: all, inbox, outbox, archived or spam.
- Scheduled Message: List and CancelAction
See the texts waiting to go out, or cancel one by message ID.
- Contact: Create or Update, ListAction
Upsert matched on phone, with tags added rather than replaced. List supports a search across name, phone, email and company, plus a tag filter.
- Device: ListAction
Paired phones with online status and last check-in.
- Spam: Flag and UnflagAction
Move a conversation to spam and mute it, or bring it back.
- Android Texter TriggerTrigger
Polls for new incoming texts on n8n's polling schedule, one item per text. It remembers the newest message it has seen, so switching a workflow off and on does not replay old texts. Filter by Phone narrows it to one sender.
Setting it up
- In n8n, open Settings, Community Nodes, Install, and enter n8n-nodes-android-texter.
- Pair a phone and create an API key in the Android Texter dashboard, under Settings, API Keys.
- In n8n, add a credential of type Android Texter API and paste the key. Saving it runs the credential test.
- Add the Android Texter node to a workflow, or the Android Texter Trigger to start one on an incoming text.
Known issues
Things people actually run into with n8n, and what to do about each one.
The trigger reacts in minutes, not seconds.
The Trigger node polls, so the delay is whatever you set under Poll Times. For instant delivery, register a webhook with the API and start the workflow from n8n's Webhook node instead: we POST a signed message.received callback the moment a text arrives. Our Zapier and Make apps use that same webhook.
A community node will not install on n8n Cloud.
n8n restricts which community nodes can be installed on its hosted plans, and that list is theirs, not ours. On self-hosted n8n the install works as described. If you are on n8n Cloud and blocked, use the HTTP Request node with the same X-API-Key header, which reaches every endpoint in our API reference.
Our landing page shows only four n8n operations.
The card is a summary and understates it. The node ships the full list above, across six resources.
An AI Agent step cannot see pictures in a conversation.
It can. Get History and Search both return media_url and media_type on every message that has an attachment. The link is signed and expires, so an agent should fetch it when it reads it rather than store it for later.
Questions
Can n8n's AI Agent use this node as a tool?
Yes. The node is usable as a tool, so an agent can send a text, read a conversation or look up a contact as part of its own reasoning.
Do I need to self-host n8n?
For installing the community node, in practice yes. Otherwise the HTTP Request node plus an API key does everything, with no node install at all.
What happens if the phone is offline when the workflow runs?
The send is queued and goes out when the phone checks in. Use Device List first if you want the workflow to branch instead of queueing.
Other ways in
- Zapier: our app, live on the zapier marketplace.
- Make: our app, listed in make's public directory.
- 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