We use necessary features to run the website and platform. With your permission, we also measure usage and performance and use marketing cookies for advertising and remarketing. Your choice applies in this browser across the website, signup and platform. Cookie policy
Closing this notice or pressing Esc lets you continue with necessary features only.
Connect Android Texter to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.
Android Texter connects Android phones to an API for sending and receiving SMS and MMS, managing contacts and devices, and automating messaging workflows.
Description and action names are the ones the vendor publishes, in English; action descriptions are shown summarized. Skyller does not alter that content.
11 ACTIONS
published by the vendor; the company enables only the necessary ones
0 EVENTS
triggers the system can send, when the vendor offers them
API KEY
each person signs in with their own credential, encrypted
APPROVAL BY RISK
sensitive actions show a card before running
Live proof
One request, one query in Android Texter and one approval.
The scene shows the path of a request; the exact actions depend on the functions your company enables in Android Texter.
Input
A team member asks, in the conversation, for something that today requires opening Android Texter — inside their area's space, with their login.
What Skyller does
01Picks, among the enabled functions, a query action and looks the information up in Android Texter with the person's own credential.
02If the request requires writing something in Android Texter, acts within permission; if the function is sensitive, it first shows the card and waits for Approve.
03Returns the result in the conversation and records who asked, which action was used and when.
Result
Android Texter stops being an open tab and starts answering inside the conversation — through the functions your company enabled.
Good to know
The available actions are the ones the vendor publishes for Android Texter; in your company only the functions turned on by the administrator are available.
If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
Being in this catalog does not mean being installed, with a valid login, working in your company.
Illustrative scene with fictitious data; no action is named because the choice depends on the functions your company enables.
Where this helps your work
Android Texter inside the conversation where the work happens.
Three common situations for people who use Android Texter every day. What Skyller does in each one depends on the functions your company turns on.
Needing to know what was agreed
“What did they decide in the project channel yesterday?”
The person asks and Skyller reads the channel in Android Texter with their login, only in the channels they belong to, and summarizes what was agreed.
Channel summary in the conversation
Notifying the team
“Tell the team the new policy has been published.”
Posting a message is a write action; with the function set to ask for approval, Skyller shows the card with channel and text and only sends it in Android Texter after Approve.
Message with approval
Administering
“A tool is one thing. A conversation channel is another.”
Here Android Texter is a tool: the AI reads and writes in it through the enabled functions. Talking to Skyller from inside Android Texter is a channel, contracted separately.
Two things, two controls
Actions and events
What the vendor offers in Android Texter.
Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.
Showing 11 of 11
Create Quick Reply
ANDROID_TEXTER_CREATE_QUICK_REPLY
Create a reusable quick-reply shortcut. The shortcut must be unique within the connected Android Texter account.
Delete Quick Reply
ANDROID_TEXTER_DELETE_QUICK_REPLY
Permanently delete one saved quick reply by ID.
Get Message Status
ANDROID_TEXTER_GET_MESSAGE_STATUS
Get the provider's current queued, sent, delivered, or failed status for a message ID returned by Send Message.
List Contacts
ANDROID_TEXTER_LIST_CONTACTS
List contacts in the connected Android Texter account, optionally filtering by name or phone text and tag.
List Conversation History
ANDROID_TEXTER_LIST_CONVERSATION_HISTORY
Return one newest-first page of inbound and outbound message history exchanged with one phone number. Pass next_cursor back as cursor to continue.
List Devices
ANDROID_TEXTER_LIST_DEVICES
List Android devices linked to the account, including IDs and online state needed to select a sending device.
List Messages
ANDROID_TEXTER_LIST_MESSAGES
List one newest-first page of messages, optionally restricting results to sent or received messages. Pass next_cursor back as cursor with the same direction to continue.
List Quick Replies
ANDROID_TEXTER_LIST_QUICK_REPLIES
List saved quick-reply shortcuts that can be reused when composing messages.
Send Message
ANDROID_TEXTER_SEND_MESSAGE
Immediately queue a real SMS or MMS to one phone number through a linked Android device. This has an external side effect and consumes message quota.
Send Messages Batch
ANDROID_TEXTER_SEND_MESSAGES_BATCH
Sequentially queue the same real SMS or MMS for 1-10 recipients. Each queued message is irreversible and consumes quota.
Update Quick Reply
ANDROID_TEXTER_UPDATE_QUICK_REPLY
Replace an existing quick reply's shortcut, title, and body.
Before you start
What your company needs to use Android Texter.
Login
Each person enters their own Android Texter API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs
An administrator connects Android Texter for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions
11 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan
Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.
Try it free with your team or book a demo: together we pick the Android Texter functions to enable and show the first approved action, with fictitious data.