Google Sheets, in every client’s workflows.

Add a row, update a row, or start when a row is added, with the client’s own Google Sheets account.

Triggers: 2start a workflow
Actions: 2steps in a workflow

Start a workflow when something happens in Google SheetsBeta

By webhook where Google Sheets sends one, by checking where it does not. A webhook is checked once a day to see it is still on, and if Google Sheets turns it off the alert carries a Reconnect button.

A row is addedPolledA new row at the bottom of a sheet, checked every 15 minutes. The first check notes what is there; rows after it start runs.
A row is changedPolledA row whose cells changed, or a new one, found by its ID column, checked every 15 minutes. The first check notes what is there. The first 5,000 rows are watched.

Do it in Google Sheets

A step with its own fields: values from the run go in by name, and what Google Sheets answers is there for the next step.

Add a rowAdd a row at the bottom of a sheet, one value per column, left to right.
Update a rowOverwrite cells in a row, left to right from where the range starts: the row an earlier “Add a row” wrote, or one you name. Cells past the last value are left as they are.

Connect the client’s Google Sheets

On the client’s page in Thrum: Add credential, type Google service account key.

In your own Google Cloud project: enable the Google Sheets API, then IAM & Admin → Service accounts → Create → Keys → Add key → JSON, and paste the file here. Then share each client sheet with the service account’s email (…@….iam.gserviceaccount.com) as an Editor. The account is yours; no Google review is needed.

The key is stored encrypted and bound to that client: another client’s workflow cannot use it, and no template or pack copies it.

Google Sheets’s API documentation

Watched like everything else

When Google Sheets stops answering or refuses the client’s key, you hear about it, and your client does not.

A failing request: Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
A service that asks for a pause: Given it, up to an hour
Requests at once, per account: 2, per worker; the rest wait their turn
Timeout: 15 seconds, unless the step sets its own
Private and internal addresses: Refused, on every redirect too
The client’s key: Encrypted, bound to the client, and kept out of every run record
A step that keeps failing: Marks the workflow Degraded and alerts you, not the client

Google Sheets and its logo are trademarks of their owner, used here only to say what Thrum works with; no endorsement is implied.

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.

Get early access See pricing