Sign-up sheet to the city database
Rows from a Google Form response sheet are loaded each hour into a PostgreSQL table used by the recreation department.
Google Sheets is where many city teams keep lists that don't have a system yet: event sign-ups, sandbag pickup logs, tree planting requests or a weekly status sheet for council offices.
SentraBridge reads rows from a sheet as records and adds a row for each record a flow sends. A sheet can feed the city database or 311, or receive a daily list from another system. Values pass through without being stored; run history keeps counts.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Rows (set range, e.g. Sheet1) | list | create | — |
Rows from a Google Form response sheet are loaded each hour into a PostgreSQL table used by the recreation department.
Each morning, yesterday's 311 requests in one council district are added as rows to that office's sheet.
New volunteers in a sheet are added to a Mailchimp audience for the parks newsletter.
Open work orders from the city database are written to a shared sheet that managers already check.
Systems cities commonly connect with Google Sheets, each with its own connector page.
Yes. A flow reads sheet rows and upserts them into SQL Server, PostgreSQL or MySQL, or reads database rows and adds them to a sheet.
The connector reads rows and appends new ones. For two-way edits, keep the system of record in a database and refresh the sheet from it.
It lets SentraBridge sign in without a person's Google login. Only sheets shared with its email address are reachable.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.