Built by someone else

Android Texter on Composio: What Works and What to Watch

Composio hosts an Android Texter toolkit so an AI agent can text through your phone with no code of your own. It wraps our public REST API and you paste your own Android Texter API key into it. We did not build it, we do not maintain it and we cannot change it: there is no partnership here, and nothing on their pages claims one. It does work, and customers use it. This page exists because two things about it will trip an agent up, and we would rather you read it here than find out mid-run.

Toolkit slug ANDROID_TEXTER. Bring your own API key.

Authentication

API key, theirs to collect. You create an atx_ key in our dashboard and paste it into Composio, which then holds it and signs calls to us with it.

What it can do

  • ANDROID_TEXTER_SEND_MESSAGETool

    One recipient. Takes an optional media URL, which queues an MMS.

  • ANDROID_TEXTER_SEND_MESSAGES_BATCHTool

    Our broadcast endpoint, as a batch send.

  • ANDROID_TEXTER_GET_MESSAGE_STATUSTool

    The delivery status of one send.

  • ANDROID_TEXTER_LIST_MESSAGESTool

    Sent and received messages, with a direction filter.

  • ANDROID_TEXTER_LIST_CONVERSATION_HISTORYTool

    One conversation by phone number.

  • ANDROID_TEXTER_LIST_CONTACTSTool

    Your contacts.

  • ANDROID_TEXTER_LIST_DEVICESTool

    Your paired phones.

  • ANDROID_TEXTER_LIST_QUICK_REPLIESTool

    Saved quick replies.

  • ANDROID_TEXTER_CREATE_QUICK_REPLYTool

    Add a quick reply.

  • ANDROID_TEXTER_UPDATE_QUICK_REPLYTool

    Edit a quick reply.

  • ANDROID_TEXTER_DELETE_QUICK_REPLYTool

    Remove a quick reply.

Setting it up

  1. Pair a phone and create an API key in the Android Texter dashboard, under Settings, API Keys.
  2. Add the Android Texter toolkit in Composio and paste the key when it asks for a connection.
  3. Tell your agent to page with a limit of up to 100 rather than with a cursor, for the reason below.
  4. If pictures matter to the task, tell the agent that every message may carry media_url and media_type, because their tool schemas do not mention either.

Known issues

Things people actually run into with Composio, and what to do about each one.

An agent paginating a long conversation reads the same page over and over.

Their list tools document a cursor parameter and tell the model to pass a next_cursor value back to get the next page. Our API has never had either: it pages with limit and page, and returns no next_cursor to hand back. So there is nothing for the model to continue with, and their tools expose no page parameter to reach page 2 with. Read what you need in one call with limit set as high as 100, and if you need to go deeper, call the API directly or use our own MCP server, both of which take page.

An agent says a message has no picture, or never mentions one.

Every one of their 11 tools publishes the same three-field output schema: data as an opaque string, error, and successful. No per-message fields are named at all, so nothing in the schema tells a model that media_url or media_type exists. The raw API response still carries both inside data, so the fix is to say so in your prompt. media_url appears on their side only as an input on the two send tools.

Nothing in the toolkit reads one message by ID, or receives texts.

Their toolkit lists 11 tools and no triggers, so an agent cannot be woken by an incoming text through Composio. For inbound, register a webhook with our API, or use our Zapier or Make instant trigger.

You found a bug in the toolkit and cannot find anywhere to report it.

Their toolkit pages publish no issue tracker, support address or chat for it. Write to us at [email protected] instead. We cannot change their toolkit, but we can tell you whether the behaviour is theirs or ours, and we talk to them about the ones that are theirs.

Questions

Is the Composio toolkit official?

No. We did not build it or review it, and their pages make no claim of a partnership with us. It is a Composio-hosted wrapper over our public API, which anyone is free to build.

Is it safe to paste my API key into Composio?

That is your call, and it is the same question as any hosted connector: Composio then holds a key that can send texts from your phone and read your conversations. If you would rather not, run our own MCP server locally, where the key stays on your machine, or call the API directly. You can revoke any key from our dashboard at any time.

What should I use instead?

If you want an AI assistant texting for you, our own MCP server does the same job, passes the full API response through so media_url is visible, and takes page for pagination. If you want a no-code automation, use our Zapier, Make or n8n connector.

Other ways in

  • Zapier: our app, live on the zapier marketplace.
  • Make: our app, listed in make's public directory.
  • n8n: our community node, on npm.
  • 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