Skip to main content
This guide is for teams that manage canned responses in bulk: importing a library from an external source, exporting a copy for review, or keeping it up to date when a single change — a new policy, a price, a product name — runs through many responses at once. By the end of this guide, you’ll have a spreadsheet that syncs your changes back to Text, a CSV copy of your existing canned responses library, and an importer that creates them from a CSV file. Each section is independent, so you can follow all or just the one that matches your goal:

Prerequisites

You’ll need:
  • A Text account with permission to create personal access tokens.
  • For the sheet: a Google account that can run Google Apps Script. A managed Google Workspace account may require its administrator to allow the script.
  • For the importer: Go 1.27 or newer, and Git, to clone and run it.

Edit canned responses in bulk

The sheet matches responses by ID. It updates and deletes the responses it imported, but can’t add responses.
1

Create a personal access token

In Text, go to Settings → API access → Personal access tokens and create a token with the canned_responses--all:rw and groups--all:ro scopes. Together these let the sheet read every response including private ones, update and delete them in any group, and show team names.
If you only manage the groups you belong to, canned_responses--groups:rw can replace canned_responses--all:rw — the sheet then imports and syncs only those groups. Keep groups--all:ro either way, or the Team column shows IDs instead of names.
Copy the Base64-encoded account_id:PAT value that Text displays, or note your account ID and the token itself. The panel accepts either.
2

Copy the sheet

Make a copy of the sheet. Each copy has its own script and its own connection details, so don’t share one writable copy between accounts.
3

Set up the template

In your copy of the template, choose Text Canned Responses from the top navigation panel and hit Set up template. Authorize the access that Google asks for.Google shows an unverified-app prompt because the script isn’t published as an add-on. Expect it for the copy you made from the link above, and don’t authorize a copy of this sheet from anywhere else.
4

Connect to Text

In the control panel, go to 1. Connect to Text and find Connection details. Select Account ID and PAT or Base64-encoded token, enter your connection details in the panel, and hit Connect.The panel keeps those details in your Google user properties and sends them only to the Text API.
5

Import your responses

Go to 2. Import responses from Text. You can limit the import to specific Team IDs, or to select Include my private responses or Include all private responses. Then, hit Import responses.The Responses tab fills from row 6. Row 5 holds these headers:Columns G to J hold the status the sheet writes as you review and sync.
6

Edit the canned responses

Edit cells in columns B to E. Use filters, find and replace, or paste values. A row you didn’t edit is never sent to Text.
  • To edit a response in a full text box instead of a cell, select any cell in its row and, in the panel, hit Load selected row in Edit a long response. Change the fields, then hit Save to sheet. This updates only the spreadsheet.
  • To delete a response, tick its checkbox in column F. Deleting a sheet row doesn’t delete the response in Text.
  • To sort, use the filter arrows in the header, so that each row moves as a whole.
An edited row shows Edited in column G until you review it.
7

Review the changes

In 3. Review and apply, hit Review changes. The sheet marks each row as Modified, Delete, or Invalid, and the Review tab lists the Before and After value of every change. Fix every Invalid row in the Responses tab, using the message in column H, then review again.When the review is correct, select I reviewed these changes. If you marked responses for deletion, also type their exact number in the confirmation field.
8

Apply the changes

Hit Apply reviewed changes, and keep the panel open until the sync finishes. Each row shows its result in column G. If the sync is interrupted, reopen the panel and hit Resume sync. Responses that already synced aren’t sent again.

Verify the sync

Synced rows show Synced in column G and a timestamp in column J. Deleted rows show Deleted. The sheet reads each response back from Text before it marks it as synced. Open a few responses in the Text app to confirm the text, shortcuts, group, and visibility you set. If a row shows Conflict, the response changed in Text after you imported it, or Text sanitized your text into a different value. Select the row, hit Load selected row, and then Compare current Text version under Resolve a conflict. Choose Keep my edits to review your edit against the Text version, or Use Text version to replace your edit for that row.

Limits

  • The sync isn’t atomic. If you hit Cancel remaining changes, the changes already applied in Text stay.
  • The sheet rejects a response longer than 45,000 characters.
  • Each import, review, and sync cycle uses the token you connected with. To switch tokens, reconnect and import again.
  • The sheet compares each response with Text before it writes, so an edit made in Text between that check and the write can still be overwritten.

Export your library to a CSV file

Use the sheet to download your canned responses as a CSV file, for example as a backup before a bulk edit or to work on them in another tool.
1

Import the responses

Create the token, copy the sheet, connect, and import, as described in Edit canned responses in bulk. Include private responses if you need them in the file.
2

Download the Responses tab

With the Responses tab active, choose File → Download → Comma-separated values (.csv). Google downloads only the active tab.

Verify the export

Open the downloaded file and confirm that it holds one row per imported response and that the ID column is filled for every row. The file has the sheet’s columns, ID to Last synced, and isn’t in the format the importer reads. To import it, for example into another Text account, build a CSV with the importer’s header from these columns:

Import canned responses from a CSV

livechat/canned-responses-import-guide
Loading repository data...
1

Create a personal access token

In Text, go to Settings → API access → Personal access tokens and create a token with the canned_responses--all:rw scope, which lets the importer create responses in any group. If you only manage the groups you belong to, canned_responses--groups:rw is enough.Copy the Base64-encoded account_id:PAT value that Text displays.
2

Clone the importer

Clone the repository and create your .env file from the example:
3

Set the token

In .env, replace the placeholder with the Base64-encoded value you copied:
.env
Instead of editing .env, you can export TEXT_API_BASIC_AUTH with the same value in your shell.
4

Prepare the CSV

The importer creates one canned response per row. Copy canned-responses.example.csv to responses.csv, then replace its rows with your own. The header must be exactly this, in this order, with a value in every column:
The file must be UTF-8. To find group IDs, use the List groups method.
5

Run the importer

The importer validates the whole file before it sends any request, so a file with an error creates nothing.

Verify the import

The importer prints Created X of Y canned responses. and exits with a nonzero status if any response wasn’t created. Open the canned responses in the Text app and confirm that the responses and their shortcuts are there.
Every run creates every row again. The importer doesn’t check for duplicates and can’t resume, so after a partial import, check which responses exist in Text and remove those rows from the CSV before you retry.
The importer continues after an error that affects one row, such as an invalid group ID, and prints it with the CSV line number. It stops on authentication, permission, rate-limit, timeout, and server errors, because retrying wouldn’t help until you resolve them. A request that times out may have created its response anyway, so check Text before you rerun that row.

A library you can audit and reuse

With the whole library in one sheet, you can do more than just editing. Audit shortcut collisions, near-duplicate responses, wording that drifted between teams, responses nobody has updated since the product changed — these show up across the set rather than in any one response. If you’re opening a new store, region, or brand, you can also use this flow instead of building a library from scratch. Export the responses you already trust, adjust the wording, set group_id to the new group, and import the file. The original library stays as it is. This is the one case where an account that migrated long ago still needs the importer.

Troubleshooting


Keep exploring

Configuration API reference
Personal access tokens