Receive SMS via Webhooks
When a customer texts the Android number, send the incoming message into your application or workflow as an event.
Turn Your Android Business Phone Into an SMS Gateway API
Keep your existing SIM and mobile number. Receive customer SMS through webhooks, send or reply from your software, route conversations to your team or CRM, and connect AI automation to the business number customers already use.
Existing Android + SIM
Inbound SMS Webhooks
Send & Reply API
AI & CRM Workflows
Business-phone first
Keep the number already used for customer enquiries.
Two-way and transactional
Receive, route, send and reply around real conversations.
Automation when useful
Connect webhooks, CRM systems, n8n, Make and AI agents.
Android SMS Gateway
Connect the SMS Already Arriving on Your Business Phone
AutoForward Text adds an API and automation layer around a normal Android phone and SIM, without turning the page into a bulk-messaging product.
Reply & Send by API
Send individual or workflow-triggered SMS through the connected phone, including replies to inbound customer conversations.
Route Messages to Your Team
Forward important SMS to email, Slack, a shared workflow or another supported destination so the message is not stuck on one handset.
Connect SMS to CRM
Use message events in customer workflows and keep business-phone conversations closer to the customer record.
How it works
From Android SMS to API Workflow
The Android phone remains the SMS endpoint. AutoForward Text connects what happens on that phone with the software your business already uses.
1
Install the Android App
Install AutoForward Text on the business phone that already contains the SIM and number.
2
Connect the Device
Pair the Android phone with your AutoForward Text account and configure the workflow you need.
3
Receive Message Events
Incoming SMS can trigger webhooks, forwarding rules, CRM actions or other business logic.
4
Reply or Send Through the Phone
Use the reply/send API when a workflow or team member needs to send an SMS back through the connected number.
Existing business number
Keep the Phone Number Your Customers Already Know
If leads, customers, tenants, patients or suppliers already text a mobile number, you do not have to move that conversation into a new number just to automate it.
The Android phone keeps receiving normal SMS
Your carrier and SIM remain the underlying messaging route.
AutoForward Text connects those messages to software
Use forwarding, webhooks, APIs and integrations around the existing number.
Humans can stay in the loop
Automation can route or draft a response while unusual conversations are handed to a person.
Transactional & conversational SMS
Built Around Real Business Conversations — Not Bulk Campaigns
The strongest use case is a business number that already receives enquiries and needs those messages connected to the people, systems and automations responsible for responding.
Customer Enquiries
Route an incoming sales, property, service or product question into your CRM, inbox or sales workflow as soon as it reaches the phone.
Appointments & Confirmations
Process replies such as confirmations, rescheduling requests or follow-up questions while keeping the conversation on the business number.
Two-Way Customer Support
Bring inbound SMS into a team workflow, let staff respond remotely, and keep the original Android phone as the sending endpoint.
Lead Assignment
Create or update a lead when a text arrives, notify the right person, and make the conversation visible beyond one handset.
Operational Notifications
Trigger individual, event-driven SMS from internal systems when a customer or team member needs a timely transactional update.
AI-Assisted Messaging
Use incoming SMS as the trigger for an AI workflow that can classify the enquiry, draft or send a reply, or hand the conversation to a person.
AI automation
Put an AI Agent Behind Your Existing Business Number
The number stays familiar to the customer. Behind it, AutoForward Text can pass the incoming SMS into n8n, Make.com or your own AI application and route an approved response back through the Android phone.
Understand the enquiry
Classify intent, extract details or look up information in your connected workflow.
Reply through the business phone
Use the reply endpoint/API so the response returns as SMS from the connected number.
Hand off when automation should stop
Route unusual or sensitive conversations to email, Slack, CRM or a human operator.
Developer friendly
Inbound Webhook. Reply Endpoint. Simple Building Blocks.
Use the gateway as plumbing between a real Android number and your software. Incoming messages trigger a webhook; your workflow decides what should happen next.
Designed for transactional workflows: customer enquiries, operational messages, individual notifications and two-way conversations — not promotional bulk blasting.
Incoming webhook
JSON{
"type": "sms.received",
"from": "+12125550184",
"content": "Is tomorrow available?",
"device_id": "36664",
"reply": {
"endpoint": "https://.../reply"
}
}Illustrative payload — use the current API documentation for exact fields.
Reply to the message
cURLcurl -X POST "{{ reply.endpoint }}" \
-H "Authorization: Bearer API_KEY" \
-H "Idempotency-Key: enquiry-001" \
-H "Content-Type: application/json" \
-d '{
"message": "Yes, tomorrow works."
}'Use a unique idempotency key when your workflow can retry a reply request.
Connect your stack
Your Android Number Can Feed the Tools You Already Use
Use forwarding for simple visibility or webhooks and APIs for deeper business logic.
n8n
n8n
Use inbound SMS as a workflow trigger and return replies through the API.
Make.com
Build visual automation for enquiries, CRM actions and AI-assisted replies.
HubSpot
Connect incoming business-phone conversations with customer records and workflows.
Pipedrive / CRM
Route relevant SMS activity into sales and customer-management processes.
Slack
Escalate enquiries or alerts to a channel when a human needs to take over.
Forward business SMS to an inbox for visibility and supported reply workflows.
AI Agents
Let an agent classify, answer or hand off inbound SMS based on your own rules and context.
Custom Webhooks
Send message events into your own application, middleware or internal systems.
Focused by design
An SMS Gateway for Business-Phone Workflows
The point is not to turn a SIM into a campaign cannon. It is to make a real mobile number programmable enough for customer communication, internal workflows and automation.
Use case
Fit
Inbound customer enquiries
Transactional notifications & follow-ups
Two-way customer support
CRM, webhook & AI automation
High-volume promotional bulk campaigns
Not the focus
Schedule SMS through this Android gateway
Choose the connected phone as the sender and select a future delivery time.
Android SMS Gateway FAQ
Questions Before You Connect a Business Phone
The phone remains part of the system, so the setup is different from renting a cloud-only SMS number.
Visit the Help CenterWhat is an Android SMS gateway?+
An Android SMS gateway uses an Android phone and its SIM as the SMS endpoint while software connects incoming and outgoing messages to APIs, webhooks or other applications. With AutoForward Text, the existing phone number can become part of a wider business workflow.
Can I keep my existing mobile number?+
Yes. That is one of the main reasons to use this setup. The Android phone keeps its existing SIM and number while AutoForward Text adds forwarding, webhook and API workflows around it.
Can I receive incoming SMS through a webhook?+
Yes. Incoming SMS can trigger webhook-based workflows so your application can process the sender and message and decide what should happen next.
Can my application reply to an incoming SMS?+
Yes. Supported gateway workflows include a Reply API so a response can be sent back through the connected Android phone and number.
Can I send SMS from an API?+
Yes. The Send API can be used for individual and transactional workflow messages through the connected Android phone. This page is not positioned around promotional bulk sending.
Can I connect the Android gateway to n8n, Make.com or an AI agent?+
Yes. A common pattern is inbound SMS → AutoForward Text webhook → n8n, Make.com or your own AI workflow → Reply API → customer. You can also route uncertain conversations to a human.
Does the Android phone need to stay powered on and connected?+
Yes. Because the Android phone and SIM are the SMS endpoint, the device needs to stay powered on and able to communicate with the service for gateway workflows to operate reliably.
Is this designed for bulk SMS marketing?+
That is not the focus of AutoForward Text's Android Gateway positioning. It is designed around business-phone messaging, inbound enquiries, transactional notifications, replies, team workflows and automation. Your mobile carrier's terms and messaging rules still apply.
Android + SIM + API
Connect Your Business Phone to the Rest of Your Workflow.
Keep the number customers already text, then add inbound webhooks, remote replies, CRM routing and AI-assisted automation around it.