Sound familiar?
What teams that collect Jotform submissions and work from a sheet tell us before a project starts.
- Submissions pile up in Jotform and I copy them into a sheet.
- The columns change whenever someone edits the form.
- Uploaded files are links I can't find again.
- Two people work on the same request because there is no status.
- A submission never reached the sheet and nobody noticed.
What we build
Each one is a working piece you can open and check when it's done.
Form fields to columns
Each question maps to a named column that stays put when the form is edited, with checkboxes, tables and name or address fields flattened into readable cells.
Google Sheets and Apps Script automation API integrations and data syncRouting to tabs and owners
Rows go to the tab for the form, type or branch you choose, and an owner column is filled from a rule such as postcode or service.
n8n, Make and Zapier automation Google Sheets and Apps Script automationFiles, edits and duplicates
Uploads are saved to a Drive folder and linked in the row, an edited submission updates its row, and the same submission arriving twice is added once.
Python scripts and utilities API integrations and data syncAlerts when a row fails
A rejected write, a renamed tab or a lapsed connection sends the submission id and cause to email or Slack, and the row is added once repaired.
n8n, Make and Zapier automationBackfill of past submissions
Earlier submissions are exported and written into the sheet in a copy first, so you check the columns before the real sheet is touched.
ETL and data pipelines Python scripts and utilitiesSummary tab and notes
A summary tab counts submissions by status and week, and notes list each question, its column and who may change it.
Dashboards and reportingThe two tools: Jotform, Google Sheets.
Also connected on request: Jotform, Google Sheets, Google Drive, Gmail, Slack.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Service requests for a property manager
Example: a property manager takes maintenance requests on a Jotform and wants each in a sheet by building, with photos linked and a status column for the crew.
Jotform webhooks, Google Sheets API, DriveExample project
Volunteer sign-ups
Example: a food bank collects shift sign-ups and wants a row per volunteer per shift, with a count of open spots updated on a summary tab.
Jotform, Google Sheets, Apps ScriptExample project
Order forms for a caterer
Example: a caterer takes event orders by form and wants them in a sheet sorted by date, with the owner told when a large order arrives.
Jotform API, Google Sheets, email alertsQuestions people ask first
Isn't there already a native connector or app for this?
Jotform has a Google Sheets integration, and for a single simple form it often does the job. We check yours first. If it fits, we set it up properly. If you need several forms routed, files handled or alerts when a row fails, we build that around it.
Will it change our existing sheet?
Only in the ways agreed. We work on a copy first and show you the columns before the real sheet is touched.
Who owns what you build?
You do. It runs in your own Jotform and Google accounts, with notes on how to change it.
How do we start?
Send us the form and the sheet you work from today. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com