Operations & Internal Tools
Connect Fillout and Google Sheets
Each enquiry becomes a project in a sheet your team already understands, at almost no running cost.
- Connects
- Fillout and Google Sheets
- Data flows
- 4 automated, two-way where safe
- Built with
- Fillout, Google Sheets, Google Apps Script
- Timeline
- Live in 3 to 5 business days from scope
- Owned by
- You, with accounts, credentials and code in your name.
In short
Connecting Fillout to Google Sheets turns each form submission into a row your team can act on. SBD built this for a five-person photo and video studio, where a Fillout enquiry form feeds Sheets, task sheets sync to an admin dashboard and running costs stay close to zero. Admin time fell by 60%.
The workflows
What runs between Fillout and Google Sheets.
Each line is one automated workflow. It shows the event in one tool, the checks and mapping in between, the action in the other tool and who is notified.
-
Lead enquiries into a sheet
-
Projects from form answers
-
Per-person task sheets
-
Live admin dashboards
Every record passes through the same stages
- 1Receive
Webhook or polling from the source tool, with a signed payload and a replay log.
- 2Validate
We check required fields, types and the record key. Anything that fails goes to the review queue.
- 3Map
Fields are mapped to the destination schema, with dropdown values, currencies and dates normalised.
- 4Upsert
Each write is matched on the record key, so a retry updates the existing record.
- 5Confirm
The outcome is logged, an alert fires if the count stops moving, and a reconciliation runs each night.
Read this first
Where the simple setup breaks down.
A one-step Zap connects Fillout and Google Sheets in an afternoon. This is what tends to go wrong once volume grows and edge cases appear.
Renaming a column can break the flow
A sheet is easy to edit, and that is the risk. If someone renames or moves a column, mapped data can land in the wrong place, so key tabs need protecting.
A row is not yet a project
A form that adds a row still leaves someone to notice it and act. A useful flow assigns an owner, sets a status and tells that person.
Form changes do not follow themselves
Adding a question to the form does not add it everywhere. The sheet and dashboard must be updated too, or the new answer gets lost.
Several people editing can overwrite work
Shared sheets are easy to clash in. One person sheet per team member, synced to a read-only dashboard, avoids most of it.
What we wire up
The data flows.
- 01 When
A lead submits the Fillout form
ThenAdd a row with the client details and create the project
- 02 When
A project is created
ThenAssign an owner and add tasks to their sheet
- 03 When
A team member updates a task
ThenUpdate the admin dashboard automatically
- 04 When
A deliverable changes status
ThenTell the client, and flag anything overdue
Used for
- Lead enquiries into a sheet
- Projects from form answers
- Per-person task sheets
- Live admin dashboards
- Client status updates
- Low-cost project tracking
- Fillout webhooks
- Protected sheet ranges
- Small studio operations
- Planning a move to SmartSuite or Retool
Built with
In every build
What every integration build includes.
Under the hood
- Upserts keyed on the record
Each write is matched on the source ID, so a retry or a re-fired event updates the existing record.
- Retries with backoff
Rate limits and timeouts are retried with increasing delays. If they still fail, they are parked for review.
- Idempotent, loop-safe writes
Two-way flows carry a marker so a change written by the sync does not re-trigger the sync.
- Reconciliation
A nightly job compares counts and totals on both sides and lists any record that differs.
- Audit log
Each run records the input, the mapping result, the action taken and what triggered it. You can search it by record.
- Error monitoring
Failed runs raise an alert. An outcome count also alerts when it stops moving, which catches failures that throw no error.
- Review queue
Records the sync is not sure about land in a screen a person can read, correct and release.
- Scoped credentials
Each connection has its own credential, limited to the objects it needs and stored encrypted in your account.
For the team
- Slack or email notifications
Alerts go to a named person on your team, by Slack, email or WhatsApp.
- A runbook
One document per integration: what it does, what each alert means, and what to do in the first ten minutes.
- Training
A live session with the people who will use the review queue, recorded for whoever joins later.
- Handover
Admin access, billing and code sit in accounts in your name from the start, so the build keeps running if we stop working together.
- Sixty days of hypercare
The engineers who built it stay on call after go-live, fix what breaks and tune what the team asks for.
- A monthly report
One page in plain language covering runs, records synced, exceptions handled and what changed.
Security and your data
Where the data goes, and who holds the keys.
- Accounts
- Every platform account is created in your name. We work through managed access you can revoke.
- Credentials
- Stored encrypted in the orchestration layer, scoped per connection and rotated at handover.
- Data in transit
- All traffic uses TLS, and webhooks are checked by signature before anything is processed.
- Data at rest
- We store only what the sync needs and keep no copies of your customer data on our machines.
- AI steps
- Where an integration uses a model, it is through a business API that does not train on your data.
- Retention
- Run logs are kept 90 days by default, which you can change. Card and ID numbers are redacted from payloads.
- Agreements
- DPA and NDA on request. Regional rules covered in our privacy policy.
Keys and sensitive data
How API keys, tokens and personal data are handled.
- Keys are kept in a vault
API keys and tokens are stored in the orchestration layer's encrypted credential store or the platform's secret manager. None are written into workflows, repos, spreadsheets or chat.
- One credential per connection
Each integration gets its own key, scoped to the objects and actions it needs. A lead sync cannot read invoices. Revoking one key stops one thing.
- Service accounts for connections
Connections use a dedicated service user in your account, so nothing breaks when a person leaves and nothing runs under someone's name.
- Two-factor on every account
Each platform account we set up has two-factor authentication on, and the recovery codes are handed to you.
- Rotation on handover and on request
Keys are rotated when the build is handed over, when anyone with access leaves, and at any time you ask.
- Secrets are redacted from logs
Audit logs redact tokens, card numbers, government IDs and anything you flag as sensitive before a line is written.
- Webhooks verified before processing
Inbound calls are checked against the sending tool's signature. Unsigned or stale payloads are dropped and counted.
- Access you can see and revoke
Our access is through managed roles in your accounts. You can see it, limit it or remove it without touching the build.
Engineering decisions
Decisions we make before writing the first workflow.
- Rate limits and backoff
Each API has a ceiling, so calls are batched, queued and retried with increasing delays during busy periods.
- Backfill and pagination
The first run loads history as well as new events. Backfills page through the source in order and resume after an interruption without writing a record twice.
- Out-of-order and duplicate events
Webhooks can arrive twice or out of sequence. Each event carries a version or timestamp, so an older version cannot overwrite a newer one.
- Schema changes
A renamed field or a new dropdown value is a common cause of silent failure. Payloads are checked against a contract, and a mismatch stops the run and raises a flag.
- Time zones, currencies, units
Dates are stored in UTC and shown in local time. Amounts carry their currency and quantities their unit, and conversions happen once, in the map step.
- Sandbox first
Builds run against sandbox or test accounts with seeded data first. Going live means switching credentials.
- Versioned and reversible
Workflows and code are version-controlled. A release can be rolled back in minutes without losing the records processed since.
- API deprecations watched
Tools retire API versions on a schedule. We track the dates for every connection in the runbook and upgrade before the cut-off.
- Cost per run known
Each run logs its cost, including any model calls, so you can see spend as it builds up.
- Run metrics
We chart runs per hour, records in and out, exception rate and latency, which often shows a problem before an alert fires.
Proof
Where we have done this.
The offer
Hire SBD to connect Fillout and Google Sheets.
We agree a fixed scope in a discovery call and go live in three to five business days. The accounts are in your name, and the engineers who built it stay on call for sixty days after.
- ScopeOne call to agree the flows, the fields and the owner, written up the same day.
- Build4 workflows, the data map above, validation, upserts, retries and reconciliation.
- Go-liveWe test in a sandbox first, then switch over. Day three to five from scope for most pairs; longer only if a tool needs approval, such as WhatsApp templates.
- HandoverRunbook, training session, alerts to a named owner, admin access and code in your accounts.
- AfterSixty days of hypercare, then a care plan or run it yourself.
Questions
What people ask about this pair.
Is a spreadsheet good enough?
For a small team with a tight budget, often yes. It stops fitting when records or permissions grow, and we plan for that move in advance.
Can we keep using the Sheets we have?
Usually. We tidy the structure and protect the columns the automation relies on, and your team keeps working as before.
Why Fillout over other forms?
It suited that build, and it can write to Sheets directly. If you already use a form tool that works, we can keep it.
Related
-
Tally and Airtable
Tally stays the book of record, and your team can see what is in it without asking accounts.
-
Airtable and Retool
Airtable is a good database with a limited interface. Retool adds the screens and permissions it lacks.
-
SmartSuite and Make
SmartSuite holds the record, and Make sends changes to the other systems within the API quota.
- Solution
Operations
The workflows we automate for this kind of team.
Fillout and Google Sheets
Connect Fillout and Google Sheets
Each enquiry becomes a project in a sheet your team already understands, at almost no running cost.
Start with a discovery call