Developer docs

Google Sheets integration

Build a specific spreadsheet read or write into your app. Check connection access, permissions, and the result before relying on it.

Catalog updated September 2026 48 catalog actions

Back to Google Sheets overview
Provider
googlesheets
Category
Other
Setup
Managed OAuth
Actions
48 listed in catalog

Start with one action

  1. Define the result. Choose one task, the data it needs, and who may run it. Start with a read when possible.
  2. Check access. Review the setup state below and the connection available to your workspace or app user. A catalog listing does not confirm that an account is connected.
  3. Inspect the current inputs. Ask the editor to discover the actions for Google Sheets and inspect the selected action's required inputs and returned data before implementing it.
  4. Verify with test data. Compare the result with what you expected. Check unauthorized access and error handling before relying on the feature.
Developer details: the supplied app client

Generated apps that include src/lib/composio.ts expose the following import in their React app code:

import { executeAction } from "@/lib/composio";

Its call signature is executeAction(actionName, params, options?). Supply the exact current action name and inputs from its specification. This import identifies the helper; it is not a complete or tested integration example.

The editor's os-list-integrations tool discovers an integration using integration_slug. Include both integration_slug and action_slug to retrieve the selected action's input and output schemas. Do not invent parameters from a catalog description.

executeAction requires a signed-in app user and any connection the action needs. The separate publicAction helper is only for a confirmed no-auth toolkit on an enabled public proxy. It does not make OAuth or API-key integrations anonymous.

Existing apps may contain an older client. Inspect the app's files and connection selection before changing a call. Keep provider credentials out of browser code and test failure handling; this guide does not promise automatic retries or synchronization.

Setup

This catalog lists managed OAuth for Google Sheets. Use the available connection flow to select the intended account and review the provider's consent request. Check whether the connection belongs to your workspace or an individual app user before adding an action.

Supported auth schemes: OAUTH2.

Catalog actions

This saved catalog snapshot lists 48 actions. Names and inputs can change. Inspect the current action specification and connection requirements before adding a call; this list is not an execution test.

Show all 48 actions
  • GOOGLESHEETS_CREATE_SPREADSHEET_COLUMN
  • GOOGLESHEETS_CREATE_SPREADSHEET_ROW
  • GOOGLESHEETS_DELETE_DIMENSION
  • GOOGLESHEETS_DELETE_SHEET
  • GOOGLESHEETS_EXECUTE_SQL
  • GOOGLESHEETS_FIND_REPLACE
  • GOOGLESHEETS_FIND_WORKSHEET_BY_TITLE
  • GOOGLESHEETS_FORMAT_CELL
  • GOOGLESHEETS_GET_BATCH_VALUES
  • GOOGLESHEETS_GET_CONDITIONAL_FORMAT_RULES
  • GOOGLESHEETS_GET_DATA_VALIDATION_RULES
  • GOOGLESHEETS_GET_SHEET_NAMES
  • GOOGLESHEETS_GET_SPREADSHEET_BY_DATA_FILTER
  • GOOGLESHEETS_GET_SPREADSHEET_INFO
  • GOOGLESHEETS_GET_TABLE_SCHEMA
  • GOOGLESHEETS_INSERT_DIMENSION
  • GOOGLESHEETS_LIST_TABLES
  • GOOGLESHEETS_LOOKUP_SPREADSHEET_ROW
  • GOOGLESHEETS_MUTATE_CONDITIONAL_FORMAT_RULES
  • GOOGLESHEETS_QUERY_TABLE
  • GOOGLESHEETS_SEARCH_DEVELOPER_METADATA
  • GOOGLESHEETS_SEARCH_SPREADSHEETS
  • GOOGLESHEETS_SET_BASIC_FILTER
  • GOOGLESHEETS_SET_DATA_VALIDATION_RULE
  • GOOGLESHEETS_SHEET_FROM_JSON
  • GOOGLESHEETS_SPREADSHEETS_SHEETS_COPY_TO
  • GOOGLESHEETS_SPREADSHEETS_VALUES_APPEND
  • GOOGLESHEETS_SPREADSHEETS_VALUES_BATCH_CLEAR
  • GOOGLESHEETS_SPREADSHEETS_VALUES_BATCH_GET_BY_DATA_FILTER
  • GOOGLESHEETS_UPDATE_DIMENSION_PROPERTIES
  • GOOGLESHEETS_UPDATE_SHEET_PROPERTIES
  • GOOGLESHEETS_UPDATE_SPREADSHEET_PROPERTIES
  • GOOGLESHEETS_UPDATE_VALUES_BATCH
  • GOOGLESHEETS_UPSERT_ROWS
  • GOOGLESHEETS_VALUES_GET
  • GOOGLESHEETS_VALUES_UPDATE

Google Sheets: a read-first example

Illustrative workflow; verify with your test sheet. Connecting Google Sheets lets your app call supported actions. It does not automatically synchronize a spreadsheet with your app's database.

Create a worksheet named QA and enter this fictional project list in cells A1:C3:

Fictional test data for QA!A1:C3
projectstatusowner
Client portalDraftAlex
Booking pageReviewSam
  1. Identify the sheet. Note its spreadsheet ID and the range QA!A1:C3. Keep this test separate from real customer data.
  2. Confirm the intended connection. The Google account needs access to that spreadsheet. Review the consent permissions and whether the app uses a workspace connection or the user's own account.
  3. Inspect a current read action. GOOGLESHEETS_VALUES_GET appears in the provider's action catalog. Ask the editor to retrieve its current input schema; do not assume Google REST parameter names match the integration's inputs.
  4. Compare the returned values. Run the read as a signed-in staff user. Compare all nine cells, including the headers: A2 should contain Client portal, B3 should contain Review, and C2 should contain Alex.
  5. Check a denied user. Sign in with a second account that has no staff role and open the same view URL. The app must deny access to these values, including a direct read request. Hiding the menu link alone is not enough.

A Connected badge alone does not prove that the chosen sheet and range are accessible. Record the actual result or error before adding more data.

Only add a write after deciding its destination, allowed columns and duplicate-submission behavior. An append and an update to a fixed range are different operations. Neither provides a built-in two-way-sync toggle.

Permissions and limits to check

The Google permission grant and your app's access rules are separate. Choosing one spreadsheet in your app does not prove the connection can access only that file. Review the actual consent scopes; Google documents both broader spreadsheet scopes and a narrower drive.file scope. Sheets scopes cannot be limited to one worksheet tab.

Decide which app users may read the returned data or trigger a write. The ordinary Sheets action path requires app sign-in. An anonymous form workflow needs separate server-side implementation and access checks; the no-auth helper does not enable it automatically.

Google quotas apply separately from Overskill credits. Handle rate-limit errors with bounded backoff and a useful error message. Do not assume polling, duplicate prevention or recovery has already been implemented.

Reviewed September 8, 2026 against the provider's Google Sheets action guide, Google's permission scopes and Google's current usage limits. These sources describe provider behavior, not a completed test of your app.

Build with Google Sheets

Describe one task you want your app to perform with Google Sheets. Check the connection requirements, then verify the result in your app. Building and running the feature may use credits; review current pricing.

Start building with Google Sheets View Google Sheets overview