Fillout connector for AI agents

CALL ANY TOOL

6 tools for forms in Fillout: list forms and read their questions, search and fetch submissions, add submissions, and delete a submission.

fillout_form_get

Get form

Get one Fillout form's metadata by its public ID. Returns id, name and questions (each with id, name and type), plus calculations, URL parameters, scheduling fields, payment fields and quiz settings when the form uses them. Use fillout_form_get to learn a form's question IDs before reading or creating submissions. Use fillout_forms_list to find the form ID.

Parameters

Name

Type

Required

Description

form_id

string

Required

Public ID of the form, as returned in formId by fillout_forms_list. Example: "foAdHjd1Duus".

fillout_forms_list

List forms

fillout_submission_delete

Delete submission

fillout_submission_get

Get submission

fillout_submissions_create

Create submissions

fillout_submissions_list

List submissions

List submissions for one Fillout form, with optional date range, status, text search, sort order and offset pagination. Returns responses (each with submissionId, submissionTime, lastUpdatedAt and question answers, plus calculations, URL parameters, scheduling, payments, quiz and login data when present), totalResponses and pageCount. Use fillout_submissions_list to browse or search a form's submissions. Use fillout_submission_get when you already have a submission ID. Get the form ID from fillout_forms_list first.

Parameters

Name

Type

Required

Description

form_id

string

Required

Public ID of the form whose submissions to list, as returned in formId by fillout_forms_list. Example: "foAdHjd1Duus".

after_date

string

Optional

Only return submissions submitted after this ISO 8601 date-time. Example: "2024-05-01T00:00:00.000Z".

before_date

string

Optional

Only return submissions submitted before this ISO 8601 date-time. Example: "2024-06-01T00:00:00.000Z".

include_edit_link

boolean

Optional

Set to true to add an editLink to each submission, a URL where the submission can be edited.

include_preview

boolean

Optional

Set to true to also return preview submissions, which were made while previewing the form in the Fillout editor.

limit

integer

Optional

Maximum number of submissions to return in this page, from 1 to 150. Fillout uses 50 when omitted. Example: 100.

offset

integer

Optional

Zero-based position to start from, for paging through results. Fillout uses 0 when omitted. To get the next page, add the limit to the previous offset (for example offset 50 with limit 50 gives the second page); pageCount in the response tells you how many pages exist.

search

string

Optional

Only return submissions whose answers contain this text. Example: "jane@example.com".

sort

string

Optional

Sort order by submission time: "asc" (oldest first) or "desc" (newest first). Fillout uses "asc" when omitted. One of: `asc`, `desc`.

status

string

Optional

Which submissions to return: "finished" (completed submissions) or "in_progress" (started but not yet submitted). Fillout returns only finished submissions when omitted. One of: `finished`, `in_progress`.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Fillout tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["fillout"], toolNames: [
    "fillout_forms_list",
    "fillout_submissions_list",
    "fillout_submission_get"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "List this week's submissions to the Beta Signup form" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["fillout"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "List this week's submissions to the Beta Signup form" }],
  tools,
});

// Execute the tool call with the user's vaulted Fillout access token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["fillout"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "List this week's submissions to the Beta Signup form" }],
  tools,
});

// Tool call runs with the user's vaulted Fillout access token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["fillout"] }, pageSize: 100,
});

const agent = new Agent({
  name: "forms_agent",
  model: "gemini-2.5-pro",
  instruction: "Fillout tools scoped to this user",
  tools,
});

await agent.run("List this week's submissions to the Beta Signup form");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Fillout tool. Click to copy, paste into your agent, done.

Forms

Copy the prompt

Copied

List every form in our Fillout account.

Copy the prompt

Copied

Show the questions on the Customer Onboarding form.

Copy the prompt

Copied

Find the form ID for the Beta Signup form.

Submissions

Copy the prompt

Copied

List submissions to the Beta Signup form from the last 7 days.

Copy the prompt

Copied

Search Event RSVP submissions that mention vegetarian.

Copy the prompt

Copied

Get the full answers for this submission ID.

Data entry

Copy the prompt

Copied

Add these 3 leads as submissions to the Contact Us form.

Copy the prompt

Copied

Record the attendee list from yesterday's workshop as Event RSVP submissions.

Copy the prompt

Copied

Delete the test submission I made on the Contact Us form today.

SEE HOW AUTH WORKS

Each user connects their own Fillout access token once, and Scalekit sends it with every call. Access tokens stay vaulted, every call is scope checked, and every action is logged.

1

Authorize

Your user connects

Fillout

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

2

Store

Their

Fillout

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

3

Resolve

When your agent calls a

Fillout

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

4

Audit

Every

Fillout

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other forms and survey connectors.

GTM and RevOps Teams

CRM AI agent

Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.

Support and Ops Teams

Support ticket automation agent

Fetches new Zendesk tickets, drafts a reply from Notion knowledge base articles, digests what it cannot answer to Slack, and archives the rest, acting as the support agent rather than a shared API key.

Test other agents

See the same per-user auth pattern across other forms and survey connectors.

GTM

CRM AI agent

Turn each Granola call transcript into a HubSpot record update, a drafted Gmail follow-up, and a Slack recap.

SUPPORT

Support ticket automation (Google ADK)

Fetch, annotate, and archive Zendesk tickets with Notion context, digesting anything it cannot answer to Slack.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Fillout access token looks fine in a demo. In production every submission the agent adds or deletes looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Fillout today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Fillout as the user or through a shared token?

As the user. Each user connects their own Fillout access token once, and Scalekit sends it with every call. Submissions the agent adds or deletes are attributed to that user in your audit trail, not a shared service account.

Where is the Fillout access token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new access token. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Fillout?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the form and submission read tools without fillout_submission_delete, which permanently removes a submission. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Fillout access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent add submissions to a Fillout form?

Yes. fillout_submissions_create adds up to 10 submissions to one form in a single call, as if respondents had filled it in. The agent calls fillout_form_get first to read the form's question IDs.

Fillout MCP server for AI agents

Tools your forms agent reaches for on Fillout, scoped per user.