Google Sheets to WhatsApp: Setup and First-Row Test

Choose the workflow before connecting the sheet

A spreadsheet can hold a contact list, invoice register or appointment queue. Start with one purpose and one trigger. For example, an accounts team may need a reminder for an unpaid invoice after checking recipient permission. The sheet needs to distinguish that business condition from a request to send a message.

Review the WhatsHub Google Sheets integration and current plans. The available sending method, templates and usage limits depend on your connection and subscription. A spreadsheet integration does not remove the rules or charges for the selected messaging provider.

Before you open the setup wizard

• Use a Google Sheet you are authorised to edit.
• Choose the connected WhatsApp sender you intend to use.
• Prepare the phone number with country code and the message fields your workflow needs.
• Use a recipient who has agreed to the test and a message appropriate for that connection.
• Keep production rows unready while testing. A ready-row action can process more than one row.
• Keep API credentials private; do not include them in shared screenshots or public example sheets.

The five setup stages in WhatsHub

The Google Sheets interface groups setup into Account, Preset, Layout Mapping, Automation and Install Script. Confirm each stage before progressing.

1. Account: choose the intended connection and sender. Verify the number shown before any test.
2. Preset: select a workflow that matches your purpose. A simple message list and an invoice reminder need different business fields.
3. Layout Mapping: map phone, message or template variables, and the status fields to the actual columns in your sheet. Changing a column header alone does not verify that mapping.
4. Automation: review the condition, schedule and stop behaviour. Begin with a manual test before enabling repeated runs.
5. Install Script: follow the instructions generated for that integration and complete its setup. Confirm the selected sheet, starting row and sender configuration. Keep credentials in the intended private configuration.

Understand the simple preset columns

The simple sending preset shown in the application uses the following layout. Treat this as that preset's example, not a requirement to rename every existing spreadsheet.

The preset describes READY → PROCESSING → SENT or ERROR. The exact delivery detail can depend on status sync, provider events and the fields mapped in your installation. SENT is not proof that the recipient read the message, paid an invoice or attended an appointment.

Run a controlled first-row test

1. Confirm every other row is outside the send condition. Check the sheet name and sender again.
2. Complete one test row with recipient permission and all required fields.
3. Mark only that row READY in the configured request column.
4. Use the installed manual send action. The generated menu also offers a batch-count action; a limit of one is useful for a first test.
5. Review the processing result, message logs and any status written back to the row.
6. Confirm that the test contact received the intended message from the intended sender.
7. Investigate any error before trying again. Do not reset a completed row to READY simply to inspect delivery.

Troubleshoot the row before widening the list

Move from a test to a payment-reminder workflow

Download the payment-reminder planning CSV to organise invoice reference, due date, amount, recipient permission and payment status. Its example row is illustrative and does not configure live sending. Map it to the workflow you actually install.

Decide who updates payment or opt-out status, what stops another reminder, and who reviews errors. Test that stop condition before scheduling repeated runs. Use message templates for wording ideas and the automation examples guide to compare related processes.

Request a Sheets setup demo with your column names, intended sender type and workflow requirement. The team can review suitability and the setup steps with you.