Forms
Fillout integration consultant: forms that start the right work
SBD connects Fillout forms to your CRM, Airtable or Notion base, Google Sheets and messaging tools, so every submission is routed, deduplicated and acted on, and a failed delivery is caught rather than discovered weeks later, for teams of 1 to 1,000 people. Workflow automation builds start at $1,000, with the fixed price set after a $500 Automation Audit that is credited to the build.
- Tool
- fillout.com
- Usually paired with
- Zite, Airtable, Notion, HubSpot
- Timeline
- Most builds live in 2 to 8 weeks
- Owned by
- You, with accounts, credentials and code in your name.
What we build on Fillout
- Route submissions to the right record and owner
- Deduplicate against existing contacts
- Start onboarding and quoting workflows from a form
- Pre-fill forms from existing records
What we sync
Workflows we are asked for
- Fillout enquiry to CRM with deduplication
- Fillout quote request to a priced proposal
- Fillout onboarding form to project setup
- Fillout to WhatsApp confirmation
Full write-ups of Fillout integrations
Tools Fillout usually needs to talk to
-

Fillout and Zite
Business apps, portals and internal tools built from a prompt on a shared Postgres database, with no per-seat pricing.
-

Fillout and Airtable
A relational database with a spreadsheet face, used as the operations base for teams who have outgrown sheets.
-

Fillout and Notion
Docs, wikis and lightweight databases, often the company brain.
-

Fillout and HubSpot
The CRM and marketing platform most B2B teams of 10 to 1,000 run on.
What a Fillout integration from SBD does
Fillout is popular with teams that live in Airtable, Notion or Google Sheets, because its forms connect to those natively and can update existing records as well as create new ones.
That covers a lot. Teams call us when a form has become the front door to a real process, such as quoting, onboarding or applications, and the process needs more than a new row.
We build four kinds of thing. Routing: a submission matched against existing contacts, assigned to an owner by rule and announced where the owner will see it. Quoting: a quote request priced from rules or a price list and returned as a proposal for review. Onboarding: a client onboarding form that creates the project, folders and tasks in one go. Confirmation: an email or WhatsApp message to the person who submitted, sent from the workflow so it is logged.
Fillout appears in one published SBD project. For a five-person photo studio, a Fillout enquiry form feeds project data straight into Google Sheets, with per-person task sheets syncing to an admin dashboard, Make for orchestration and Apps Script and Cloudflare Workers for heavier processing. Admin time fell by 60%.
When Fillout's native integrations are enough
If a submission only needs to create or update a record in Airtable, Notion or a sheet, Fillout's native integrations are usually the right answer and we will tell you so. Its forms can also look up and update existing records in those tools, which removes a lot of the duplicate problems other form tools create, so we check what the native connection already does before proposing anything custom. A custom workflow earns its cost when:
- A submission must be checked against existing records in a CRM before anything is created.
- One submission must start work in three or four systems, in order, with a record of each step.
- Pricing, eligibility or routing logic is too involved for form logic alone.
- You need to know within minutes when a delivery fails, before anyone opens the results page.
Fillout's API, webhooks and failure handling
- 01
Fillout's REST API uses an API key sent as a bearer token, from Settings, Developer.
Its help centre, read in October 2026, sets a limit of 5 requests a second per key, and 10 a minute for creating or deleting submissions. Organisations hosted in the EU use a separate base URL, eu-api.fillout.com, and calling the wrong region returns an error naming the right one. Regenerating the key invalidates the old one at once, so key rotation needs every integration updated in the same window. In-progress, unfinished submissions are available through the API only on Business, Team and Enterprise plans.
- 02
Webhooks come in two modes.
Simple sends the whole submission as JSON. Advanced sends only the fields you map, with your own headers. When a webhook fails, Fillout marks the submission with an error on the results page, and you can retry that integration once the problem is fixed. Fillout's webhook article does not describe an automatic retry, and its alternative, resubmitting a response, reruns every integration, workflow and notification on the form, which can create duplicates elsewhere.
- 03
So our receivers answer quickly and queue the work, and we pair every webhook with a scheduled check that lists recent submissions through the API and processes any that did not arrive. A receiver outage then costs a short delay and no lost leads, and nobody has to press resubmit.
Fillout plans and the data behind the form
Fillout is now a product of Zite: the company renamed itself in March 2026, and Zite apps can share a database with Fillout forms.
Fillout's pricing page in October 2026 lists a Free plan with 1,000 responses a month, Starter at $15 a month billed annually with 2,000, Pro at $40 with 5,000, and Business at $75 with unlimited responses and custom domains. SSO and audit logs are listed on Enterprise, which is priced on request.
The form is only as good as the data behind it. Where a form updates existing records, we pass a record ID in the URL so the right record is updated, rather than matching on a name someone typed. Dropdown options that drive routing are kept in step with the values in the destination system, and changes to them are reviewed.
Form patterns that keep downstream data clean
- 01
Most integration problems start in the form.
We use URL parameters to pre-fill and pass record IDs whenever a form is sent to a known person, so the submission arrives already linked. Answers that drive routing use fixed options rather than free text. Uploaded files are named and stored by the workflow in the client's folder instead of sitting only as attachments on the submission.
- 02
Long forms are split into steps with logic, so people only see the questions that apply to them, which raises completion and keeps optional fields optional. Where unfinished submissions matter, such as long applications, the plan needs to include in-progress submissions, which Fillout's API documentation ties to Business, Team and Enterprise.
- 03
Every form that starts a process has a named owner, and a test submission is run through the whole chain after any change to its fields.
- 04
Where a form is embedded on your website, the page and the form are tested together on a phone, because most submissions now come from one.
Hidden source and campaign parameters are passed from the page into the form, so marketing can see which page and which campaign produced each enquiry without a separate tracking tool. When a form is retired, its links are redirected and its webhook removed, so old links do not quietly collect submissions nobody reads.
How a Fillout engagement with SBD works
- Step 1$500Automation AuditCredited to the build
- Step 2from$1,000Workflow automationFixed after the audit
- Step 3from$3,000Internal toolsFixed after the audit
- Step 4from$50Care planA month, after sixty days of hypercare
Every engagement starts with an Automation Audit at $500, credited in full to your build. We review your forms, where submissions go, what happens next by hand and where things get lost. Workflow automation builds start at $1,000, internal tools at $3,000 and multi-module systems at $5,000. Work runs in two-week sprints with sixty days of hypercare, and care plans start at $50 a month. See the pricing page. You pay Fillout directly.
What you own when we finish
Everything below is in your name when the build ends.
- The Fillout account, API key, workflow platform and destination systems are in your name.
- You receive a map of each form, its URL parameters, the fields that drive routing and every system it writes to, plus a runbook for failed webhooks and key rotation.
- Your team can edit questions and wording; changes to routing fields come back through review.
Fillout at enterprise scale
Fillout is used by operations, sales and people teams that already keep data in Airtable, Notion or Google Sheets, for enquiries, quotes, onboarding, applications and internal requests. In larger organisations several teams build their own forms, and the forms quietly become the entry point to important processes.
Sign-in and audit
Fillout lists SSO and audit logs on Enterprise. We confirm what your plan includes and keep integration access on one documented API key with a rotation procedure.
No silent failures
Webhook receivers queue work and alert on errors, and a scheduled API check processes any submission that did not arrive, so nobody needs to resubmit and risk duplicates.
Data residency
For EU-hosted organisations we use Fillout's EU API address and keep downstream storage in the agreed region.
Clean records
Record IDs travel in form URLs, submissions are matched before anything is created, and dropdown values are kept in step with the destination system.
Form ownership
We list each live form with its owner, destination and the fields that drive routing, so teams know what they can change and what needs a review.
Engagements we take on
Already on Fillout, quotes still priced by hand
A quote request form lands in a base and someone prices it later. We price from your rules or price list, draft the proposal and hold it for a person to review before it is sent.
Already on Fillout, onboarding in five systems
We turn one onboarding form into the project, folders, tasks and welcome message, in order, with each step logged and failures alerted.
Already on Fillout, submissions going missing
We find which deliveries failed, recover them through the API, and add the queue and scheduled check that stop it happening again.
Read next
Sources
- Fillout Help Center, Fillout REST API (authentication, rate limits, EU base URL, plan notes), checked 29 October 2026
- Fillout Help Center, Send form submissions to a webhook (modes, failures, retry and resubmit), checked 29 October 2026
- Fillout, Pricing page (plans, responses a month, Enterprise features), checked 29 October 2026
Standards on every build
Validation, retries, reconciliation, audit logs and alerts come as standard, with credentials and accounts in your name. Read the integration standards
What people ask about Fillout
Fillout or Typeform?
Fillout where the destination is Airtable or Notion, Typeform where the design matters most. Both have webhooks we can build on.
Start with the one Fillout workflow your team still runs by hand
Bring it to a discovery call. You leave with a yes or no on fit, an outline of the build and what we would do first.
Book the call











