Integration

Google AppSheet integration

Google AppSheet builds no-code apps on top of tables (Google Sheets, Excel, databases and AppSheet Database). Through the AppSheet API an agent can read a table's rows (all, by key, or with a Selector expression such as FILTER or TOP), add rows, update rows by key, delete rows by key, and run one of the app's data-change actions on given rows. Writes go through the app's own rules: formulas, Valid_If and Required checks, and the app's automations run for each changed row; reads and writes run as the app owner unless a user email is given, and security filters apply. The API is available on AppSheet Enterprise plans only and must be enabled per app (Settings > Integrations > IN: from cloud services to your app). Authentication is the app's Application Access Key, sent in the ApplicationAccessKey header, with the App ID shown on that same Integrations pane and the AppSheet host of the account's data residency region (www.appsheet.com, eu.appsheet.com or asia-southeast.appsheet.com); one connection reaches one app.

Connect Google AppSheet How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Google AppSheet.Built from the 5 Google AppSheet tools below, on the connection you add once.

What you can do with Google AppSheet

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

add_rowsAdd rowsPOSTAdds one or more rows to an AppSheet table and returns them as stored. Initial values, app formulas and Required and Valid_If checks apply; automations triggered by app data changes run for each row.
delete_rowsDelete rowsPOSTDeletes rows of an AppSheet table, found by their key column values, from the app's data source and returns the deleted rows. Automations triggered by app data changes run for each row.
find_rowsFind rowsPOSTReads rows of an AppSheet table: all rows, the rows whose keys are given in rows, or the rows a selector expression picks and orders. Returns every column, virtual ones included. Holds whatever the table stores.
invoke_actionInvoke actionPOSTRuns one of the app's own actions (a data-change action, or a grouped action made only of data-change actions) on rows given by key, then returns the updated rows. The app's automations, if any, run too.
update_rowsUpdate rowsPOSTUpdates rows of an AppSheet table found by their key column values and returns them as stored. Columns left out keep their value; "" clears a text column. Automations triggered by app data changes run per row.

Use Google AppSheet from Claude Code, Cursor or Codex

Connect Google AppSheet in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google AppSheet operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Google AppSheet

Create your workspace
Sign up free. Nothing to install.
Connect Google AppSheet once
Add your Google AppSheet connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.