Fillout
Read Fillout forms and their submissions, import submissions, and subscribe webhooks, over the Fillout REST API v1.
About
Fillout ships in the w6w first-party pack. It declares 8 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.fillout- Version
- 0.1.3
- Author
- w6w
- Licence
- MIT
- Categories
- Forms & Surveys · Productivity
Overview
Fillout is a form builder, and this app covers its entire public API: reading which forms exist, pulling their submissions, creating a submission programmatically, and subscribing a webhook so a workflow hears about new responses as they arrive.
Because that’s the whole surface Fillout currently exposes, there’s no larger feature set held back — a workflow gets everything a form owner could automate today. Submissions come through with any file uploads already resolved to URLs, so downstream steps can fetch an attachment without needing a separate storage flow. Deleting a submission or a webhook is available too, each safe to retry without creating a duplicate.
What isn’t here is anything Fillout itself doesn’t support well from outside its own dashboard: there’s no API for a form’s design, and Fillout’s third-party OAuth path is still gated behind vendor approval, so this app authenticates with a straightforward account-level key instead — simpler to set up and just as capable for reading and moving submission data.
Build with Fillout
Three routes to the same 8 actions. The Workflow tab is generated from Fillout's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get Form Metadata
form-get Fetch one form's questions, calculations, URL parameters and other metadata by form ID.
Create Submissions
submission-create Import up to 10 submissions into a form. Does not trigger the form's notifications, workflows or integrations.
Delete Submission
submission-delete Permanently delete one submission from a form. There is no undo.
Get Submission
submission-get Fetch a single submission by its ID, with every question response it carries.
Get Submissions
submission-list List a form's submissions, with date, status, text-search and pagination filters.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Fillout's real ids.
{
"manifestVersion": "2",
"name": "fillout-example",
"steps": [
{
"id": "form-get",
"uses": {
"app": "io.w6w.fillout",
"action": "form-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"formId": "<formId>"
}
}
]
}Here are some of the things you can do
-
Get Form Metadata
readform-get -
Get Forms
readform-list -
Create Submissions
performsubmission-create -
Get Submission
readsubmission-get -
Get Submissions
searchsubmission-list
+3 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Fillout, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Fillout. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "submission-create",
payload: {
formId: "<value>",
submissions: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action submission-create --payload '{"formId":"<value>","submissions":"<value>"}'Give an AI agent Fillout — without giving it Fillout's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.fillout#form-get",
"input": {
"formId": "<formId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Fillout connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Fillout's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Fillout itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Fillout declares its own checks, so its health is a property of the app rather than something the host guesses at.
Fillout platform status
Component status from Fillout's Statuspage (branded Zite). Covers the respondent-facing forms, the form editor, workspaces/admin, the Developer API this app calls, and the Zite database, apps and app editor.
API request-rate headroom
Fillout allows 5 requests per second per account/API key and reports the remaining count in IETF ratelimit-* headers. Read from GET /v1/api/forms without parsing the body.