Google Sheets integration

What it does

The Google Sheets integration lets your agency push data into a client's spreadsheets and react to new rows without leaving TaskJuice. Connect a client's Google account once and you can append rows, update ranges, batch-update multiple ranges in one call, clear cells, read values back, create entirely new spreadsheets, and start a workflow whenever a new row lands in a watched sheet.

Connect a Google Sheets account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Google Sheets and click Connect.
3. Sign in with the Google account whose spreadsheets you want to manage on behalf of your client.
4. Grant the requested scopes (full read and write access to Sheets, plus read-only access to Drive so TaskJuice can list selectable spreadsheets).
5. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access at any time, visit Google Account permissions and remove the TaskJuice entry.

Triggers

• google-sheets/new-row polls a selected sheet on a configurable interval and emits one activation per cycle containing every row observed in the watched range. Drop a Loop node downstream to process each row individually, or feed the array straight into a digest.

Actions

• google-sheets/append-rows appends one or more rows to the end of a selected sheet, with control over how values are parsed and whether to overwrite or insert.
• google-sheets/update-cells writes a block of values into a specific A1 range, replacing whatever is there.
• google-sheets/batch-update-values updates multiple ranges in a single request, useful when one workflow needs to fan writes across several sections of a sheet.
• google-sheets/clear-range removes the contents of a range without deleting the row or column structure.
• google-sheets/get-values reads a range back out, with options for how cells, dates, and the major dimension are rendered.
• google-sheets/create-spreadsheet creates a new Google Spreadsheet under the connected account.

Known limitations

• Google Sheets does not publish webhooks for in-sheet changes. The new-row trigger polls on a configurable interval (60 seconds minimum, five minutes by default), so latency is bounded by the chosen interval rather than instant.
• The Sheets API enforces per-user and per-project quotas. When a 429 is returned, TaskJuice surfaces it as a retryable rate-limit error and respects the recommended backoff.
• Selectable spreadsheets are loaded through the Drive API, so the connection must include the read-only Drive scope. Spreadsheets the connected user cannot see in Drive will not appear in the resource picker.