Fillout

Work with Fillout forms and their data. Agents list forms, retrieve and create submissions, and delete records, making form responses available to downstream workflow steps the moment you need them.

6 actions API key available

Fillout website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A scheduled sweep runs against the vendor intake form every ten minutes

List Submissions pulls completed responses since the last run, with answers, calculations, and URL parameters

Get Form maps question IDs to field names so answers land in the right columns

Each vendor's details are upserted into the operations database and logged to the tracking sheet

Submissions with missing tax details or unrecognized payment terms are flagged as exceptions

Exceptions post to the operations channel with the full response attached

The operations lead reviews each exception and decides whether to approve the vendor, request a correction, or reject the intake

What This Integration Enables

Most form tools treat the API as an export chute: responses out, nothing in. Fillout's API works both directions, and that changes what a form is. A Fillout form becomes the canonical intake dataset for a process: web respondents write to it through the form, and FlowRunner agents write to it through Create Submissions when the same data arrives by phone, email, or migration. One dataset, one reporting view, regardless of which door the data came through. And because the question set itself is readable through the API, workflows map answers by question ID instead of by position, which means the form's owner can keep improving the form without breaking the automation behind it. - Sweep submissions with filtering by completion status, date range, and free-text search across answers - Retrieve single submissions in full detail, including calculations, URL parameters, and quiz scores - Read a form's question set with IDs and types, so answer mapping is derived, not hardcoded - Create submissions programmatically, up to 10 per request, from data collected anywhere - Preserve URL parameters and calculation results alongside answers for attribution and scoring - Keep the permanent deletion of responses behind [human-in-the-loop](/concepts/human-in-the-loop) review

Without FlowRunner

Responses wait for an export Form data sits in the dashboard until someone downloads a CSV and re-keys it

Answer mapping is tribal knowledge Which question feeds which CRM field lives in one person's memory

Data flows one direction only Records collected by phone or email never make it into the form's dataset

With FlowRunner

Submissions move on a schedule Sweeps filter by status and date and land responses in the CRM, sheet, and channel

Mapping is read from the form itself Get Form supplies question IDs and types, so field mapping survives form edits

The form becomes a two-way dataset Create Submissions writes records collected elsewhere back into the same reporting view

Use Case Scenarios

Lead forms that feed the CRM without a Friday export

The demo request form collects company, role, use case, and the UTM parameters riding on the URL. An agent sweeps List Submissions filtered to completed responses after the last run, calls Get Form once to refresh the question map, and creates each respondent in [HubSpot](/integrations/hubspot) with answers mapped to properties and the UTM source preserved. High-scoring leads, computed from the form's own calculation fields, also post to [Slack](/integrations/slack). Marketing edits the form freely; because mapping is read from Get Form, adding a question does not silently break the sync.

The paper channel joins the dataset

An event team collects registrations through Fillout, but a partner also emails a spreadsheet of fifty attendees. Instead of maintaining two lists, the agent reads the rows from [Google Sheets](/integrations/google-sheets), maps each to the form's question IDs from Get Form, and writes them with Create Submissions in batches of ten. Every downstream report, and every other workflow sweeping this form, now sees one complete dataset. The form's own analytics reflect reality instead of just the web channel.

Quiz scoring with a human on the borderline

A certification quiz runs on Fillout. The agent sweeps completed submissions, reads each quiz score from Get Submission, and processes the clear cases automatically: passes get their certificate generated and logged, clear fails get the retake email. Scores within the borderline band route to a person with the full answer set attached, because a certification decision at the margin deserves eyes on the actual answers, not just the number. The reviewer decides, and the agent executes whichever path they choose.

Human-in-Loop Highlight

Delete Submission is permanent, and a form submission is usually the only copy of what a person said: there is no upstream system to restore it from. The tempting automation is a cleanup sweep that purges test responses by pattern, and the failure mode is that a real respondent used the word "test" in an answer, or a real vendor submitted during the QA window. So deletion runs as a proposal, never a reflex. The agent assembles the candidates: "14 submissions matched the test-data filter on the vendor intake form: 11 from internal email domains, 3 unmatched. Full answers attached." A person clears the three unmatched entries as genuine, approves the eleven, and Delete Submission runs on exactly those. An agent can always re-run a sync. Nobody can re-ask a respondent what they said.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

6 actions

Forms

List Forms Returns all forms in the account with each form's unique ID and name. The discovery step that supplies form IDs to every other operation.
Get Form Returns a form's metadata and full question set, including each question's ID, name, and type. The mapping step that keeps answer routing correct as forms evolve.

Submissions

List Submissions Returns a form's submissions with pagination and filtering by completion status, date range, and free-text search, sorted by submission time. Each result includes answered questions, calculations, and URL parameters, up to 150 per page with a total count. The sweep step behind every sync workflow.
Get Submission Returns a single submission by ID with all answered questions, their IDs, names, types, and values, plus calculations, URL parameters, and quiz score when applicable. Used to pull full detail before a decision or an escalation.
Create Submissions Programmatically creates one or more submissions for a form, up to 10 per request, with each answer referencing a question ID from Get Form and optional URL parameters. The write path that makes a form a two-way dataset.
Delete Submission Permanently deletes a single submission by its ID and returns a confirmation. This action cannot be undone, and it is the operation this page's human gate exists for.

Frequently Asked Questions

What can FlowRunner do with Fillout?

FlowRunner agents can run List Forms, Get Form, and List Submissions in Fillout, plus 3 more actions.

Does connecting Fillout to FlowRunner require OAuth?

No. Fillout connects to FlowRunner with an API key, no OAuth flow required.

Can Fillout trigger a FlowRunner workflow automatically?

Fillout doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Fillout

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us