Turn eligible spreadsheet rows into practical business texts sent from your own Android phone and mobile number.
Google Sheets holds the message data. Zapier, Make, or n8n decides which row can run. VoxiSMS sends the SMS through the connected phone, SIM, and active mobile plan.
Quick answer
VoxiSMS is the Android SMS delivery step for teams that manage message jobs in Google Sheets. A Zapier, Make, or n8n workflow reads an eligible row, maps its phone and message fields, and asks VoxiSMS to send from the business's own Android phone, SIM, real number, and active mobile plan.
See every approved VoxiSMS connection pathKeep the sheet simple enough to inspect before the automation runs. These columns separate eligibility, recipient data, message content, and the final result.
| Column | What it controls | Example value |
|---|---|---|
| send_sms | Controls whether this row is eligible to enter the workflow. | YES |
| phone | Stores the recipient number in the format expected by your automation. | +1 202 555 0142 |
| first_name | Adds a useful personal field without writing a full message by hand. | Jamie |
| message_type | Chooses the approved template for an appointment, order, lead, payment, or service update. | service_eta |
| message_data | Holds the variable that makes the message useful, such as a date, order number, or arrival window. | 2:00–4:00 PM |
| sms_status | Records a pending, sent, or failed result so completed rows can be skipped. | pending |
Store approved message templates in the automation, then map only the fields that change from row to row. Start with the business SMS template library when the team still needs approved copy for the workflow.
| Use case | Fields from the row | Example text |
|---|---|---|
| Appointment reminder | first_name, appointment_time, location | Hi [first_name], your appointment is on [appointment_time] at [location]. Reply if you need to change it. |
| Order ready | first_name, order_number, pickup_point | Hi [first_name], order [order_number] is ready at [pickup_point]. Reply here if you have a question. |
| New enquiry | first_name, enquiry_topic, owner_name | Hi [first_name], [owner_name] received your enquiry about [enquiry_topic] and will follow up shortly. |
| Payment reminder | first_name, invoice_number, due_date | Hi [first_name], invoice [invoice_number] is due on [due_date]. Reply if you need the payment details again. |
| Field-service update | first_name, arrival_window, technician_name | Hi [first_name], [technician_name] is due between [arrival_window]. Reply here if access details have changed. |
All three paths keep Google Sheets as the data source and VoxiSMS as the delivery step. Choose the builder your team already uses.
Start with the published new-row template and map the recipient and message. Add the eligibility filters and status update described below before enabling the complete workflow.
Zapier's current Google Sheets integration lists new-row, new-or-updated-row, updated-row, and row-update operations.
Use Google Sheets modules to watch or select rows, apply filters, pass each eligible row into VoxiSMS, and write the result back into the same sheet.
Make's current Google Sheets documentation covers connecting a sheet and working with spreadsheets, rows, cells, and change-based scenarios.
Start with a Google Sheets Trigger, filter eligible rows, and map the recipient and message into the VoxiSMS node. Update the row with the result so completed messages can be skipped.
The n8n Google Sheets Trigger supports rows being added, updated, or both. Follow the VoxiSMS guide to install and connect the node.
Start with one trigger, one eligibility filter, one VoxiSMS action, and one row update. That is enough to test the complete route.
Use Google Sheets Zap templateThe template starts with a new row and a Send SMS action. Add the filters and row update below to complete this workflow.
Keep one header row and one message job per row. Add the phone, message type, template data, send flag, and status fields before building the Zap.
Use New Spreadsheet Row when appending fresh work, or New or Updated Spreadsheet Row when a controlled field change should start the Zap.
Continue only when send_sms is YES, the phone and required message data are present, and sms_status is not already sent.
Choose the connected Android device, map the phone field, and build the message from the approved template and row values.
Use your own number or another approved test recipient. Check the rendered message, sender number, and reply path before switching the Zap on.
Write the result and send time into sms_status and sent_at. The next trigger can then skip a completed row.
Make is a useful fit when the scenario needs scheduled checks, several filters, or a controlled set of rows handled in one run.
Review the VoxiSMS Make integrationAdd the Google Sheets connection, choose the file and worksheet, and retrieve a small test set so each column is available for mapping.
Use a row-based module that matches the workflow: watch new work as it arrives, or select a defined set during a scheduled scenario.
Require the send flag, phone number, message data, and an unsent status before the route can continue.
Map the row's phone and message fields into the VoxiSMS Send SMS module and select the Android device that should send it.
Run a single controlled row through the scenario, receive the SMS, and check that a reply reaches the workflow destination you configured.
Update the sheet after the VoxiSMS step so successful and failed rows remain visible without relying on staff memory.
The sheet stores business data and the automation maps it. VoxiSMS then asks the registered Android phone to send through its own SIM and active carrier plan. Customers see the real mobile number and can reply to it.
Keep the row, filter, automation, VoxiSMS step, Android sender, and recipient in one visible path.
Swipe horizontally to inspect each workflow step.
A controlled test row shows whether the trigger, fields, message, Android device, and status update agree.
Clear answers about triggers, worksheet columns, multiple rows, replies, and Android delivery.
Google Sheets stores the rows but does not send the text by itself. Zapier, Make, or n8n reads an eligible row and passes its phone and message data to VoxiSMS, which sends through the connected Android phone.
VoxiSMS connects to Google Sheets through Zapier, Make, or n8n. The sheet is the data source, the automation handles triggers and filters, and VoxiSMS is the SMS delivery step.
Start with a send flag, phone number, message type, required template data, and send status. Add a timestamp or reference ID when the team needs to trace the result back to a business record.
Yes. Zapier, Make, or n8n can process eligible rows one at a time. VoxiSMS fits moderate operational workflows such as reminders, order updates, lead follow-up, and service messages rather than high-throughput mass marketing.
Yes. The recipient replies to the real mobile number in the connected Android phone. Use the VoxiSMS inbound trigger in Zapier or n8n, or the Make inbound setup, to pass replies into the next business step.
No. VoxiSMS adds no per-message fee. The connected Android phone sends through the mobile plan already active on its SIM.
Install VoxiSMS on an Android phone, connect Google Sheets through Zapier, Make, or n8n, and test one eligible row from trigger to received SMS.