Update items from rows
When a row is updated in Google Sheets, update the item in Reach.at.
See all Reach.at + Google Sheets integrations or talk to a human
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Reach.at Explore Reach.at →
TriggersFires when a new page or post is published on Reach.at.
Fires when a form on Reach.at is submitted.
Fires when a CMS item is updated on Reach.at.
Publishes or updates a page on Reach.at.
Creates a new CMS item on Reach.at.
Updates existing content on Reach.at.
Google Sheets Explore Google Sheets →
TriggersFires when a row is added to a sheet in Google Sheets.
Fires when a row or column changes in Google Sheets.
Fires when a new spreadsheet or worksheet is created in Google Sheets.
Adds a new row to a sheet in Google Sheets.
Updates the values in an existing row in Google Sheets.
Finds a row by a column value in Google Sheets.
More Reach.at + Google Sheets workflows
See all Reach.at + Google Sheets integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Update items from rows” between Reach.at and Google Sheets?
Yes — describe it in the box above and Knit's Integrations Agent researches Reach.at and Google Sheets's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Can rows create pages or posts?
Yes. When a row is added in Google Sheets, Reach.at can create a post or collection item.
Can new content be logged?
New or updated items in Reach.at can be added as rows in Google Sheets.