You can send SMS from Google Sheets with a short Apps Script: read a phone number and message from each row, post it to a texting API with UrlFetchApp, and write the result back to the sheet. It works well for a few hundred texts to people who've agreed to hear from you, and it gets awkward fast after that.

This post gives you a working script for Ready's API, then covers batching, the quota and timeout limits you'll hit, and the signs that a sheet has stopped being the right tool. Only text people who opted in or who've replied to you. A sheet makes it easy to paste in a list, and that's exactly where consent mistakes happen.

What you need before you start

  • A Ready API key, from your account settings. Treat it like a password.
  • A sheet with one phone number per row in E.164 format (+12125550199), a message column, and a status column.
  • A list of people who agreed to receive texts. If you can't point to where each number opted in, don't send.

If your numbers are a mix of formats, clean them first. The E.164 formatting post shows the cases that trip people up.

Keep the API key out of the sheet

Don't paste the key into a cell or into the script body. Anyone with edit access to the sheet or the script can read both. In the Apps Script editor, open Project settings, add a script property named READY_API_KEY, and read it at run time. For key hygiene beyond that, see API key security and rotation.

The script

Ready's send endpoint is POST /v1/messages on https://api.tryready.com, with the key in an X-API-Key header. The body is to, body and consent_attested. Set consent_attested to true only when the list really is a consented one, because it's your promise that the recipient agreed to texts.

function sendFromSheet() {
  var key = PropertiesService.getScriptProperties().getProperty('READY_API_KEY');
  var sheet = SpreadsheetApp.getActiveSheet();
  var rows = sheet.getDataRange().getValues();
  // Columns: A phone, B message, C status, D idempotency key
  for (var i = 1; i < rows.length; i++) {
    if (rows[i][2]) continue; // already handled
    var idem = rows[i][3] || Utilities.getUuid();
    sheet.getRange(i + 1, 4).setValue(idem);
    var res = UrlFetchApp.fetch('https://api.tryready.com/v1/messages', {
      method: 'post',
      contentType: 'application/json',
      headers: { 'X-API-Key': key, 'Idempotency-Key': idem },
      payload: JSON.stringify({
        to: String(rows[i][0]),
        body: String(rows[i][1]),
        consent_attested: true
      }),
      muteHttpExceptions: true
    });
    var code = res.getResponseCode();
    var inProgress = code === 409 && JSON.parse(res.getContentText() || '{}').code === 'idempotency_in_progress';
    if (code === 429 || code >= 500 || inProgress) {
      Utilities.sleep(3000); // leave C empty; the key stays in D, so the next run retries this row
      continue;
    }
    sheet.getRange(i + 1, 3).setValue(code);
  }
}

Three details matter here. The Idempotency-Key is saved in column D before the call, so if the script times out and you run it again, a retried row won't send twice. muteHttpExceptions keeps one bad row from killing the whole run. And the status column gets the HTTP code, so you can filter for failures afterward. A 429, a server error or a 409 idempotency_in_progress (the first attempt is still running) leaves the status empty, so the next run retries that row with the same key. The full request and error list is in the messages docs and the error docs.

Send in batches with the bulk endpoint

One call per row is fine for small lists, but it's slow. When every row gets the same text, use POST /v1/messages/bulk with {"to": [...], "body": "...", "consent_attested": true}. It takes at most 100 recipients per call, so slice your column into chunks of that size or smaller. See the bulk messages docs.

Per-row messages with a first name in them need the single endpoint. Bulk sends one body to everyone.

Limits and pitfalls

PitfallWhat happensWhat to do
Script run timeApps Script stops a long run mid-loopProcess a chunk per run, rely on the status column to resume
Daily URL fetch quotaCalls start failing once you pass itCheck Google's current quota page for your account type, and use bulk to cut calls
Trigger overlapTwo runs hit the same rowsWrite the status before the call, or take a script lock
Leading zeros, lost plus signsSheets reformats numbersFormat the column as plain text
Opted-out contactsThe send is refused up front and not chargedRead the status column, remove those rows from your list
Quiet hoursAn API text is held only if the window opens within 6 hours, otherwise it isn't sentRerun the row once the window opens

Google changes its quotas, so check them rather than trusting a number in a blog post, ours included.

When to outgrow a sheet

A sheet is a fine start. Move on when you need any of these:

  • Replies handled by a person, which means an inbox, not a status column.
  • Opt-outs flowing back into your list automatically.
  • More than one person editing the list at once.
  • Scheduled campaigns with quiet-hour handling across time zones.

At that point, use the Ready app's contact import and campaigns, or call the API from a small service. The Excel and CSV import guide covers the no-code route. Standard pricing is on the pricing page, and you can start at /signup.

Frequently asked questions

Can Google Sheets send text messages by itself?

No. Sheets has no built-in SMS. You add an Apps Script that calls a texting API, or use an add-on or automation tool.

Is it safe to put the API key in the script?

Put it in script properties instead of in the code or a cell. Anyone who can edit the script can still run it, so share the sheet narrowly.

How do I stop a rerun from texting people twice?

Save an idempotency key per row before sending and reuse it on a retry. Also skip any row that already has a status.

Do I need 10DLC registration to text from a sheet?

For US business texting on local numbers, yes, registration applies no matter how you call the API. Ready handles it in the app. See the 10DLC explainer.