Appearance
Google Sheets integration
There are two directions, and they solve different problems.
Studio reads and writes your sheet. A playbook step reads a range, does work per row, and writes results back into the sheet.
Your sheet calls Studio. A share link gives one sheet access to one playbook or one dashboard, with no API key in the spreadsheet.
What the Google Sheets integration can do
| Direction | Step or method | Behaviour |
|---|---|---|
| Studio reads a sheet | Sheets read step | Reads a named range or a whole tab into the playbook as structured rows |
| Studio writes a sheet | Sheets write step | Appends rows to a sheet, or replaces a named range outright. A range write is last-write-wins, so point it at a range Studio owns |
| Sheet reads Studio | =IMPORTDATA on a dashboard share link | Live dashboard data in a sheet, refreshed by Sheets |
| Sheet calls a playbook | =IMPORTDATA on a playbook share link | Runs the playbook on a cell value and returns the answer |
| Apps Script calls a playbook | POST to a share link | Processes a column of rows through a playbook |
What the Google Sheets integration can be used for
Google Sheets can be used for bulk enrichment, running an AI step over hundreds of rows without anyone pasting a prompt hundreds of times.
Google Sheets can be used as a lightweight front end for a workflow, where the people doing the work already live in a spreadsheet and do not want another tool.
Google Sheets can be used for review and correction, writing generated output into a sheet where a human edits it before it goes anywhere.
Google Sheets can be used for live dashboard extracts, so a finance or management sheet pulls current numbers rather than a stale paste.
Google Sheets can be used for classification and deduplication runs, where a column of messy input becomes a column of clean labels.
Google Sheets can be used without handing out an API key, because a share link is scoped to exactly one capability and revocable.
Google Sheets combined with other integrations
| Combination | What it gives you |
|---|---|
| Sheets + Odoo | Bulk changes staged in a sheet, reviewed, then applied to the ERP |
| Sheets + company brain | Every row answered from your own documents rather than from general knowledge |
| Sheets + dashboards | Live warehouse figures inside the sheet a stakeholder already opens |
| Sheets + webhooks | A row change kicks off a downstream process |
What you need to connect Google Sheets
- Google OAuth authorisation from Studio, for the read and write steps
- Or nothing at all beyond a share link, if the sheet is the caller
To connect: Configure → Connections, then Connect Google Account. This is org-wide — every Sheets read/write step in every playbook for that org uses this one connection.
Troubleshooting a stuck connection
The green "Connected" state only confirms the stored token can still be refreshed. It does not confirm the account can reach any specific sheet, or that Google granted Sheets access at all. Work through these in order if a connection looks fine but a real read or write fails.
"Connections" isn't in the sidebar. Try the /integrations URL directly — the page itself isn't restricted, only the sidebar link can be hidden by an org setting. An admin needs to turn the Integrations feature back on for the org.
"redirect_uri_mismatch" when clicking Connect. Google is rejecting the request before you even reach a consent screen — the OAuth client's Authorized redirect URIs are missing the one Studio actually sends. This is a Google Cloud Console setting, not something a Studio admin can fix from inside Studio; contact whoever manages the Google Cloud project.
Connect succeeds, but every real read or write fails. This is the confusing one, because the connection looks completely healthy. Two separate things can cause it:
- Google granted a narrower set of permissions than Studio asked for — reconnect and check carefully for any Google warning about the app or its permissions during the consent screen, rather than clicking through quickly.
- Your Google Workspace administrator has restricted which third-party apps can access Sheets and Drive data, and this app isn't on the allowed list yet — even though your personal consent succeeded. This is a Workspace admin setting (Security → API Controls → App Access Control), not something visible from inside Studio, and can take a while to take effect after being changed.
If neither explains it, a fresh disconnect-and-reconnect (confirming the right Google account in any account picker Google shows) resolves most remaining cases.
Frequently asked
Do I need a Google Workspace account? No, a Google account with access to the sheet is enough.
Does the sheet formula expose a secret? No. A share link carries an encrypted payload, is rate limited, expires, and can be revoked without touching anything else.
Can it write to a sheet a colleague owns? Yes, if the connected account has edit access to it.
Will it overwrite my formulas? A range write replaces everything in that range. Give Studio its own tab or its own columns and read from them with formulas, rather than pointing a write at a range people edit by hand.