Skip to main content
connic

Google Sheets

Run an agent on every new row in a spreadsheet and write its results back as new rows, through your own Google service account.

Modes
Inbound, Outbound
Set up in
Dashboard or connectors/*.yaml
Documentation
Google Sheets docs
Publisher
By connic

Every new row starts a run

connic checks the sheet about every minute and gives each new row to every linked agent, keyed by the column names in row 1.

Columns as fields
Each row arrives as an object with one key per column name, formatted the way the sheet shows it. The agent reads Name or Email instead of cell positions.
Form responses work
Rows that a form, a script or a paste adds in one go start one run each. Empty rows are skipped.
Safe with inserted rows
Insert or delete rows above, and connic finds where it left off. Edits to rows it already processed start nothing.
google-sheets-payload.json
{
  "row": {
    "Name": "Jane Doe",
    "Email": "jane@example.com",
    "Company": "Example Ltd",
    "Seats": "40",
    "Message": "We want to roll this out in January."
  },
  "row_number": 41,
  "_google_sheets": {
    "connector_id": "550e8400-e29b-41d4-a716-446655440000",
    "spreadsheet_id": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms",
    "sheet": "Form responses",
    "row_number": 41,
    "timestamp": "2026-10-13T07:12:31.204518"
  }
}

Results land as new rows

An outbound Google Sheets connector appends the agent's JSON output below the sheet's data. Each key fills the column with the same name.

Columns by name
Keys match the column names in row 1. Missing keys leave cells empty, and a key without a column fails the delivery with its name.
Nothing overwritten
connic inserts each row below the data, so existing rows and anything under them stay as they are.
Values stay values
Text that starts with = stays text and never runs as a formula. Send after every run, as a tool the model calls, or from middleware.
output.json
{
  "Name": "Jane Doe",
  "Email": "jane@example.com",
  "Score": 82,
  "Next step": "Book a demo"
}
Qualified
Name        Email              Score  Next step
Tom Berger  tom@example.com    54     Send pricing
Jane Doe    jane@example.com   82     Book a demo

Shared with one address

connic signs in as a service account in your Google Cloud project. It sees only the spreadsheets you share with its email address.

Viewer or Editor
Inbound connectors read with Viewer access. Outbound connectors need Editor to append rows.
No delegation
Spreadsheets don't need domain-wide delegation. Remove the service account from the sharing list, and connic loses access.
One Connection for Google
The same Google Workspace Connection serves Gmail connectors, so one service account covers mail and spreadsheets.
Google Sheets · Share
Share "Inbound leads"

Add people and groups
  connic-agents@acme-agents.iam.gserviceaccount.com

Role
  Viewer   inbound: read new rows
  Editor   outbound: append rows

Keep the sheet next to your agents

Declare the connector in connectors/. The service account key lives in a Connection that the file names, so secrets stay out of your code and each environment can read its own sheet.

connectors/inbound-leads.yaml
type: google_sheets
mode: inbound
name: Inbound leads
connection: acme-google
config:
  spreadsheet: 1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms
  sheet: Form responses
agents:
  - lead-qualifier
environments:
  Staging:
    config:
      sheet: Test responses
  Production: {}
create: connectors/inbound-leads.yaml (google_sheets)

Where Google Sheets fits

Pick a setup to see what arrives, which agent runs and what goes out.

Each form response lands in a sheet, and the agent scores it into a second sheet for sales.

Form responses
Inbound Google Sheets
lead-qualifier
Row in Qualified
google-sheets-payload.json
{
  "row": {
    "Name": "Jane Doe",
    "Email": "jane@example.com",
    "Seats": "40"
  },
  "row_number": 41
}
output.json
{
  "Name": "Jane Doe",
  "Email": "jane@example.com",
  "Score": 82,
  "Next step": "Book a demo"
}

The agent answers support email and calls a sheet tool to log each request with its category.

Support mailbox
Inbound Gmail
support-triage
Row in the ticket log
gmail-payload.json
{
  "from_address": "sam@example.com",
  "subject": "Change delivery address for ord_9035",
  "body_text": "Please ship it to my office instead.",
  "has_attachments": false,
  "attachments": []
}
tool-call.json
{
  "row": {
    "Date": "2026-10-13",
    "From": "sam@example.com",
    "Category": "Address change",
    "Order": "ord_9035"
  }
}

Your team adds products with their specs, and the agent writes a description for each one.

Product sheet
Inbound Google Sheets
product-writer
Row in Descriptions
google-sheets-payload.json
{
  "row": {
    "SKU": "LMP-204",
    "Product": "Desk lamp",
    "Specs": "LED, 3 brightness levels, oak base"
  },
  "row_number": 118
}
output.json
{
  "SKU": "LMP-204",
  "Description": "A warm LED desk lamp with three brightness levels on a solid oak base."
}

A schedule starts the agent every morning, and yesterday's numbers land as a new row.

Daily at 07:00
Cron Scheduler
daily-metrics
Row in Daily KPIs
cron-payload.json
{
  "trigger": "cron",
  "schedule": "0 7 * * *",
  "triggered_at": "2026-10-13T07:00:00.000Z",
  "prompt": "Collect yesterday's support numbers"
}
output.json
{
  "Date": "2026-10-12",
  "Tickets": 61,
  "Median first reply (min)": 34,
  "Solved by agent": 44
}

Google Sheets FAQ

No. connic signs in as your own service account with its key. You share each spreadsheet with the service account's email address, as you would with a colleague. The docs show the setup.

No. At its first check it starts after the sheet's last row, so linking an agent to a full sheet doesn't start a run for every old row.

Edits to rows that were already processed start nothing. When rows are inserted or deleted above the last processed row, connic finds that row at its new place and goes on after it.

No. connic writes values as they are, so text that starts with = stays text and never runs as a formula.