Connect a Google Sheet or Airtable base as a trigger for an AI employee. When a row is added or updated, your employee picks up the change and acts on it, no separate automation tool required. This channel is on the roadmap and not available to hire against yet.
A lot of real work still starts life as a spreadsheet row: a new lead dropped into a shared sheet, a support ticket logged in Airtable, an order status flipped from pending to paid. Right now that row just sits there until a person reads it and decides what to do next.
Spreadsheet Channel is built to close that gap. Once it ships, you point an AI employee at a Google Sheet or Airtable base, and a new row or an edited row becomes the same kind of trigger a Slack message or an incoming email already is on this platform: the employee wakes up, reads the row, and works the task using its normal skills and tools.
The difference from a generic spreadsheet automation tool is that the thing on the other end is an employee with context, not a single-purpose script. A Zapier-style row trigger can move data or send a notification; it cannot read the rest of the row, check your CRM, draft a reply in your voice, and update the sheet when it is done. Because the trigger lands on an AI employee that already knows your business, the row is a starting point for judgment, not just a payload.
This channel has not shipped yet. It is on the roadmap, and this page describes what it is designed to do, not something you can turn on today.
It helps to know how the channels that already work are built, because Spreadsheet Channel is designed to join them rather than sit beside them. Whether a request arrives from the chat box, a Slack message, an email, a phone call, or a scheduled trigger, it is turned into plain text plus a little context and handed to the same single pipeline. Your employee then runs with its full persona, skills, duties, tools, and memory, and the answer is routed back out to wherever the request came from. A spreadsheet row is simply one more way in.
That shared shape is what makes the difference practical rather than theoretical. Adding a channel does not give you a second, weaker version of your employee that only knows about spreadsheets. The employee that would read your row is the same one you talk to in chat, with the same connected apps, the same instructions, and the same history of what it has already done for you. Nothing has to be configured twice.
Every conversation records which channel it started in, so work stays traceable to its source rather than turning into an anonymous pile of activity. That is how you can already tell a Slack request apart from a scheduled one today, and it is the same mechanism a connected sheet is designed to use. When this ships, a row that triggers work will be identifiable as a row.
Plenty of real workflows never leave a spreadsheet: intake forms that dump into a sheet, a shared Airtable base tracking leads or inventory, a manually maintained status column. Spreadsheet Channel is aimed at exactly that setup, so you do not have to migrate the sheet into a different system before an AI employee can work from it.
The goal is to let the sheet stay the source of truth for the people who already use it, while an employee handles the parts of the row that are actually work: qualifying a lead, following up on an order, flagging a value that looks wrong.
Spreadsheet Channel is a trigger, not a database. It is meant to start work when a row changes, not to become the employee's storage layer for structured data; for that, an employee reading from a connected tool through its normal skills is still the right approach.
It also is not a spreadsheet automation product like a formula engine or a generic row-to-webhook connector. Those move data between systems. This channel exists specifically to hand a row to an AI employee that can read it, decide what it means, and do the surrounding work.
You do not have to wait for this channel to get work out of a spreadsheet. An employee with a connected Google Sheets or Airtable account can already read a sheet, write back to it, and act on what it finds when you ask it to, either in conversation or on a routine you schedule. What is missing today is the trigger: you decide when to look, rather than the sheet telling your employee that something changed.
That gap is exactly what this channel is meant to close. Until it arrives, a recurring routine that checks a sheet on a cadence you choose is the closest working equivalent, and the connection, the instructions, and the skills you set up for it stay useful afterwards. Nothing you build now becomes wasted effort.
A row change becomes a task for an AI employee
You will connect a specific Google Sheet or Airtable base to an AI employee, the same way you connect a channel like Slack or Mailbox today: pick the employee, pick the sheet, and tell it which column or view matters.
When a row is added or a watched column changes, the employee treats that row as an incoming task. It reads the row's data, does the work with whatever skills and tools it already has (drafting outreach, updating a linked tool, researching a company), and can write results back to the sheet so the row reflects what happened.
Because it is a channel like any other, activity coming through a connected sheet shows up in the employee's normal conversation and work history, so you can see exactly which row triggered which task.
A form or a manual process drops new leads into a shared Google Sheet. Once this ships, an employee can pick up each new row, research the company, and draft a first outreach message without anyone copying the row into another tool.
A team tracks orders or support tickets in Airtable and updates a status column by hand. A watched status change could hand the row to an employee to follow up, notify the customer, or escalate, using the row's own data as context.
Sheets that are updated by hand drift: missing fields, inconsistent values, obvious typos. An employee triggered on new or edited rows could flag or correct issues as they appear instead of waiting for a periodic manual review.
Small teams often run a content calendar or a campaign tracker as a spreadsheet with a status column. Marking a row ready could hand it to a marketing employee to draft the piece, prepare the assets, and mark the row done, without anyone moving the plan into a different tool first.
| Before | After |
|---|---|
| A new row sits in the sheet until somebody notices it and decides what to do about it. | The row itself is designed to wake an AI employee that reads it and works it, so intake stops depending on somebody remembering to look. |
| Before automation can touch a sheet, the data has to be copied into a system that automation understands. | The sheet is designed to stay exactly where it is, still the source of truth for the people already using it every day. |
| A row trigger can fire one fixed action, so anything needing judgement still waits for a person to pick it up. | The row will go to an employee that knows your business and can research, draft, and decide what that particular row actually needs. |
| When something goes wrong you cannot tell which row caused which piece of work, or whether it ran at all. | Work triggered by a connected sheet is designed to land in the employee's normal conversation and work history, where you can read it back. |
No. It is on the roadmap and not open to hire against yet. This page describes the design so you know what is coming, not a feature you can turn on today.
Both are the planned targets: a Google Sheet or an Airtable base connected as the trigger source for a specific AI employee.
The plan is to trigger on a new row being added or an existing row being updated, so you can use it for intake (new rows) or status changes (edited rows) depending on how your sheet is structured.
The design lets the employee write results back into the sheet, so a row can show both what came in and what the employee did about it, not just the original data.
Those tools move data or fire a single action when a row changes. Spreadsheet Channel hands the row to an AI employee that already has context on your business and can use its full set of skills and tools to decide what the row actually needs, not just execute one fixed step.
No. The Spreadsheet Channel is designed so a connected Google Sheet or Airtable base can wake your AI employee directly, with no middleman service sitting between the sheet and the work. You connect the sheet to the employee once, and the employee handles what happens next using the skills and connected apps it already has.
Yes, that is the intent. Every conversation on the platform already records which channel it came in through, whether that was chat, Slack, email, or a schedule, and a connected sheet is designed to work the same way. Work triggered by a row will appear in the employee's normal conversation and work history, identifiable as having come from the sheet.
Spreadsheet Channel is part of Ways you talk to them.
Chat in the app with live reasoning, speak to your AI voice agent over a call, message on Slack or WhatsApp, send an email, or embed a widget on your website. Every channel connects to the same AI agent with the same memory and capabilities. Switch channels mid-conversation and your employee picks up right where you left off.