# Fillout Forms AI integration on Definable

> Fillout is a platform that allows users to create and manage forms, offering a REST API for programmatic access to form data.

## What this connects

Fillout is a platform that allows users to create and manage forms, offering a REST API for programmatic access to form data.

Vendor: https://www.fillout.com/

## Tools available

**22** tools available. First 12:

- `FILLOUT_FORMS_AUTHORIZE_O_AUTH` — Authorize OAuth — Tool to initiate the OAuth authorization process for third-party applications. Use when you need to generate the URL to redirect your users to the Fillout consent page.
- `FILLOUT_FORMS_CREATE_DATABASE` — Create Database — Tool to create a new Zite database instance with tables and fields. Use when you need to create a structured database in Fillout with custom tables and field definitions. Each database must have at least one table, and each table must have at least one field.
- `FILLOUT_FORMS_CREATE_DATABASE_WEBHOOK` — Create Database Webhook — Tool to create a webhook subscription for a Fillout database. The webhook will receive HTTP POST notifications when subscribed events occur (e.g., record.created, record.updated, record.deleted). Use when you need to set up real-time notifications for database changes. Maximum 100 webhooks per database.
- `FILLOUT_FORMS_CREATE_FIELD` — Create field — Tool to add a new field to an existing table with specified type, name, and configuration. Use when you need to extend a database table with additional columns.
- `FILLOUT_FORMS_CREATE_RECORD` — Create record — Tool to create a new record in a Fillout table with the provided field data. Use when you need to add a new entry to a specific table in your Fillout database. The record parameter should be a dictionary where keys are field names (or field IDs) from your table schema, and values are the data to store in those fields.
- `FILLOUT_FORMS_CREATE_TABLE` — Create table — Tool to add a new table with custom schema to an existing database. Use when you need to create a structured table in a Fillout database with specific field definitions. Each table must have at least one field.
- `FILLOUT_FORMS_DELETE_DATABASE` — Delete database — Tool to permanently delete a database and all its data including tables, fields, views, and records. Use when you need to completely remove a database. Warning: This action cannot be undone.
- `FILLOUT_FORMS_DELETE_DATABASE_WEBHOOK` — Delete database webhook — Tool to remove a webhook subscription from a Fillout database. Use when you need to delete an existing webhook from a specific database.
- `FILLOUT_FORMS_DELETE_FIELD` — Delete field — Tool to permanently delete a field from a table. Use when you need to remove a field from a Fillout database table. Note: Cannot delete the primary field.
- `FILLOUT_FORMS_DELETE_RECORD` — Delete record — Tool to permanently delete a record from a table in Fillout Database. Use when you need to remove a specific record. This action cannot be undone.
- `FILLOUT_FORMS_DELETE_TABLE` — Delete table — Tool to permanently delete a table and all its data including fields, views, and records from a Fillout database. Use when you need to remove a table. This action cannot be undone.
- `FILLOUT_FORMS_GET_DATABASE_BY_ID` — Get database by ID — Tool to retrieve detailed information about a specific database including all tables, fields, and views. Use when you need to get comprehensive database structure and metadata by database ID.

## Auth

Auth schemes: `API_KEY`.

## How agents use Fillout Forms

Inside a Definable workflow, Fillout Forms is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Fillout Forms** — the Researcher (GPT-5.5) pulls context from Fillout Forms (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Fillout Forms** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Fillout Forms (create record, post message, draft email).
- **Designer / Engineer → Distributor → Fillout Forms** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Fillout Forms (attach file, open PR comment, post status).

The Verifier checks every Fillout Forms call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- forms & surveys — https://definable.ai/apps/category/forms-&-surveys/

## Related

- HTML page: https://definable.ai/apps/fillout_forms/
- Same category (forms & surveys): https://definable.ai/apps/category/forms-&-surveys/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt