Fillout is a platform that allows users to create and manage forms, offering a REST API for programmatic access to form data.
Fillout is a platform that allows users to create and manage forms, offering a REST API for programmatic access to form data. On Nagent, Fillout Forms is exposed as a fully-configurable forms & surveys integration that any agent can call — 22 actions, and API key authentication. No code is required to wire Fillout Forms into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Fillout Forms to automate the kinds of tasks forms & surveys teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Fillout Forms into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Fillout Forms, with input parameters and output schema. Drop these into any step of an agent built in Helix.
FILLOUT_FORMS_AUTHORIZE_O_AUTHTool 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.
Input parameters
An arbitrary string to maintain state between the request and callback. It will be returned to your redirect URI.
The client ID of your OAuth application in Fillout, found in Developer settings.
The URL to which users will be redirected after granting or denying authorization.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_CREATE_DATABASETool 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.
Input parameters
The name of the database to create.
Array of table definitions to create in the database. Each table must have a name and at least one field. At least one table is required.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_CREATE_DATABASE_WEBHOOKTool 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.
Input parameters
The destination URL that will receive HTTP POST requests when subscribed events occur. Must be a valid HTTPS URL.
Array of event types to subscribe to. At least one event must be specified. Common events include record.created, record.updated, and record.deleted.
Optional: Filter webhook notifications to events from a specific table only. If omitted, the webhook will receive events from all tables in the database.
Unique identifier of the database to create the webhook for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_CREATE_FIELDTool 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.
Input parameters
Field name
Field type (e.g., single_select, single_line_text, date, number, checkbox, email, url, phone, multi_select, long_text, attachment, formula, lookup, rollup, created_time, last_modified_time, created_by, last_modified_by, autonumber, barcode, button, count, currency, duration, last_modified_by, percent, rating, relation)
Table identifier (accepts either ID or table name)
Field-specific configuration options. For single_select or multi_select types, this should contain an 'options' array with objects having 'label' and 'color' properties. For other field types, this may contain type-specific configuration.
The database's unique identifier
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_CREATE_RECORDTool 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.
Input parameters
Record data with field names or field IDs as keys and their corresponding values. The keys should match the field names or IDs in your table schema. Values can be strings, numbers, booleans, or null.
Unique identifier of the table (or table name) where the record will be created.
Unique database identifier. This is the ID of the database containing the table where you want to create a record.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_CREATE_TABLETool 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.
Input parameters
The name of the table to create.
Array of field definitions for this table. Each table must have at least one field. Each field requires a type, name, and template object.
The unique identifier of the database where the table will be created.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_DELETE_DATABASETool 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.
Input parameters
The unique identifier of the database to permanently delete. Warning: This operation cannot be undone and will delete all data including tables, fields, views, and records.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_DELETE_DATABASE_WEBHOOKTool to remove a webhook subscription from a Fillout database. Use when you need to delete an existing webhook from a specific database.
Input parameters
Webhook identifier to delete
Unique database identifier
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_DELETE_FIELDTool 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.
Input parameters
Field ID or name to delete. Cannot delete the primary field.
Table ID or name.
Unique database identifier.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_DELETE_RECORDTool 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.
Input parameters
Unique table identifier (or table name)
Record identifier (UUID)
Unique database identifier
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_DELETE_TABLETool 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.
Input parameters
The table identifier to delete. Accepts either the table ID or table name.
The unique identifier of the database containing the table to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_GET_DATABASE_BY_IDTool 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.
Input parameters
The unique identifier of the database
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_GET_DATABASESTool to retrieve a list of all databases for your organization. Use when you need to list available databases after authenticating with Fillout.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_GET_FORMSTool to retrieve a list of all forms in your account. Use when you need to list your forms after authenticating with Fillout.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_GET_RECORD_BY_IDTool to retrieve a single record by its UUID with all field data. Use when you need to fetch detailed information for a specific record from a Fillout table.
Input parameters
Table ID or name
Record's unique identifier (UUID)
Unique database identifier
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_INVALIDATE_ACCESS_TOKENRevokes an OAuth access token obtained from Fillout's OAuth authorization flow. Use this action when a user logs out, disconnects their account, or when you need to programmatically revoke a third-party app's access to Fillout data. Important notes: - This action is for OAuth tokens only, NOT for API keys - OAuth tokens are obtained via the OAuth flow (authorize -> token exchange) - The operation is idempotent: invalidating an already-invalidated token succeeds - After invalidation, the token can no longer be used for API requests Example: A user disconnects your app from Fillout - call this to revoke their access token.
Input parameters
The OAuth access token to revoke. Must be a valid token obtained from Fillout's OAuth flow (not an API key). Do not include the 'Bearer' prefix - just the raw token value.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_LIST_DATABASE_WEBHOOKSTool to retrieve all webhook subscriptions configured for a specific database. Use when you need to list, audit, or manage existing webhooks for a database.
Input parameters
Unique identifier for the database. This is the database ID for which you want to retrieve all configured webhook subscriptions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_LIST_RECORDSTool to retrieve records from a Fillout table with filtering, sorting, and pagination. Supports complex filter conditions using AND/OR logic and 14 operators (equals, contains, greater_than, in, is_empty, etc.). Use when you need to query table data with specific conditions or retrieve paginated results.
Input parameters
Sort criteria with field ID and direction. Records are sorted by creation time ascending if omitted.
Number of records to return per page (default: 500, max: 2000)
Query conditions with AND/OR logic. Structure: {"and": \[{"field": "Status", "operator": "equals", "value": "Active"}\]} or {"or": \[...\]}. Operators: equals, does_not_equal, contains, does_not_contain, starts_with, ends_with, is_empty, is_not_empty, in, not_in, greater_than, greater_than_or_equal_to, less_than, less_than_or_equal_to. Supports nested AND/OR groups.
Number of records to skip for pagination (default: 0)
Unique identifier or name of the table to retrieve records from
Unique identifier of the database containing the table
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_REMOVE_FORM_WEBHOOKTool to remove a webhook by its ID. Use when you need to delete an existing webhook from your Fillout account.
Input parameters
The ID of the webhook you received when you created it
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_UPDATE_FIELDTool to modify field properties and configuration for an existing field in a Fillout database table. Use when you need to update field names or change field configuration settings.
Input parameters
New field name to update the field with.
Field ID or name to update.
Table ID or name where the field exists.
Updated field configuration object containing field settings and properties. The structure varies by field type.
Unique database identifier where the table is located.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_UPDATE_RECORDTool to update specific fields of an existing record in a Fillout table. Use when you need to modify particular fields without affecting other fields in the record. Only the fields specified in the request will be updated.
Input parameters
Field key-value pairs to update. Keys are field names, values can be strings, numbers, booleans, or null depending on the field definition in your table.
Table identifier (ID or name)
Record identifier (UUID)
Database identifier
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FILLOUT_FORMS_UPDATE_TABLETool to update table properties like name. Use when you need to modify table metadata such as renaming a table in a Fillout database.
Input parameters
New table name to update. Only provided fields will be updated.
Unique identifier of the table. You can also use the table name instead of the ID.
Unique identifier of the database containing the table.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 87 agents privately built on Nagent that already use Fillout Forms.
Build on Nagent
Connect Fillout Forms to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Fillout Forms, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Fillout Forms is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Fillout Forms is connected, you configure its 22 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Fillout Forms steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Fillout Forms event fires, the agent kicks off automatically.
Every Fillout Forms action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Fillout Forms ships with 22 pre-built forms & surveys actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Fillout Forms together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Fillout Forms-based workflows tailored to your business.