[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Fillout API and MCP server

> Fillout has a REST API that lists forms, reads a form's questions and its submissions, creates and deletes submissions and manages webhooks, but it cannot create or edit forms, and Fillout documents no MCP server for the form builder (checked 17 Oct 2026). Zite, Fillout's sister product, has an MCP server that can view the Fillout forms in a workspace, and its docs say creating forms is not supported over MCP.

Form builder for surveys, quizzes and lead forms: over 50 field types, page and field logic, and responses that go to Results or a connected database.

## What is the Fillout API?

Cotlet's Fillout API exposes 15 endpoints for your own Fillout account: list forms, get form, get form logic, list submissions, get submission, get form settings, create form, add question, update question, set question logic, set page branch, update form access, set email notifications, publish form and delete submission. The list_forms endpoint returns forms in your Fillout account with their IDs and names. Each endpoint takes simple JSON inputs like form_id, submission_id or label and works both as an operation of the fillout_read or fillout_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Productivity & teams](https://cotlet.dev/integrations/category/productivity-teams.md)
- **Endpoints:** 15 (6 read, 9 write)
- **Updated:** 2026-10-20

Fillout has a REST API that lists forms, reads a form's questions and its submissions, creates and deletes submissions and manages webhooks, but it cannot create or edit forms, and Fillout documents no MCP server for the form builder (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Fillout with 15 endpoints (6 read, 9 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Fillout have an official API?

Fillout has a REST API that lists forms, reads a form's questions and its submissions, creates and deletes submissions and manages webhooks, but it cannot create or edit forms, and Fillout documents no MCP server for the form builder (checked 17 Oct 2026). Zite, Fillout's sister product, has an MCP server that can view the Fillout forms in a workspace, and its docs say creating forms is not supported over MCP.

| Task | Fillout official | Cotlet |
|---|---|---|
| List your forms | Yes: REST API, Bearer key from Developer settings | Yes |
| Read a form's questions | Yes: Get form metadata returns questions, calculations and URL parameters, not logic | Yes |
| Read and filter submissions | Yes: REST API, up to 150 per call, 5 requests per second per key | Yes |
| Delete a submission | Yes: REST API | Yes |
| Create a form with its questions | No: Form Agent does it only in the editor; the Zite MCP does not create forms | Yes |
| Add or edit questions | No: Form Agent does it only in the editor | Yes |
| Set show or hide rules and page branches | No: Form Agent can set up page logic only in the editor | Yes |
| Close a form, set dates or a response limit | No: Form Agent does not manage form-level settings | Yes |

Sources: [Fillout Help: Fillout REST API](https://www.fillout.com/help/fillout-rest-api), [Fillout Help: Create submissions (API reference)](https://www.fillout.com/help/api-reference/create-submissions), [Fillout Help: Build forms with Form Agent](https://www.fillout.com/help/form-agent), [Zite Help: Zite MCP overview](https://zite.com/help/database/mcp/mcp-overview)

## For AI agents

```text
Fillout has a REST API that lists forms, reads a form's questions and its submissions, creates and deletes submissions and manages webhooks, but it cannot create or edit forms, and Fillout documents no MCP server for the form builder (checked 17 Oct 2026). Zite, Fillout's sister product, has an MCP server that can view the Fillout forms in a workspace, and its docs say creating forms is not supported over MCP.
Cotlet provides a hosted MCP server and REST API for Fillout: 15 tools (6 read, 9 write).
Access       Sign up at https://cotlet.dev/app/signup?app=fillout, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    fillout_read, fillout_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/fillout, each operation at its own route, e.g. PATCH /api/v1/fillout/forms/{form_id}/access
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_forms, get_form, get_form_logic, list_submissions, get_submission, get_form_settings, create_form, add_question, update_question, set_question_logic, set_page_branch, update_form_access, set_email_notifications, publish_form, delete_submission
Confirm      update_form_access, set_email_notifications, publish_form, delete_submission (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/fillout-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=fillout, requests Fillout in the Cotlet console and creates an API key there.
2. The user signs in to Fillout once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Fillout for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Fillout server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Fillout MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Fillout in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Fillout only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Fillout login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Fillout's terms; Cotlet is not affiliated with Fillout.
```

## What can an AI agent do in Fillout?

Cotlet is best for agencies and teams that build many Fillout forms and want their AI agent to create them, set their logic and close them on time without running or fixing a server.

- **[Build a form from a brief](https://cotlet.dev/integrations/fillout-api-mcp-server/build-form-from-brief.md)**: "Build a Fillout form called "Webinar registration" with four questions: full name, work email, company size as a dropdown (1-10, 11-50, 51+) and what they want to learn. Read it back to me, then publish it with responses saved only in the form." → `create_form`, `add_question`, `get_form`, `publish_form`
- **[Add branching logic to a form](https://cotlet.dev/integrations/fillout-api-mcp-server/add-form-logic.md)**: "In "Discount application", skip the "Describe your organization" question unless the company type is Non-profit, and send students straight to the Accepted ending page and private companies to Rejected." → `get_form`, `get_form_logic`, `set_question_logic`, `set_page_branch`
- **[Close a form on a date or after a response limit](https://cotlet.dev/integrations/fillout-api-mcp-server/close-form-after-deadline.md)** (runs: weekly): "Every Monday, go through my Fillout forms that have an expiration date, and for "Autumn event" set it to 30 November 2026 23:59 with the closed message "Registration is closed. See you next year." Tell me which forms are already closed." → `list_forms`, `get_form_settings`, `list_submissions`, `update_form_access`
- **Weekly form responses digest** (runs: weekly): "Every Monday, list the responses my "Contact us" form got last week, group them by topic and tell me which ones still need an answer." → `list_submissions`, `get_submission`
- **Delete test submissions**: "Find submissions in "Webinar registration" whose email ends in @example.com or whose name is "test", show me the list and delete them after I confirm." → `list_submissions`, `delete_submission`

## Can Fillout automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Fillout connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to close a form on a date or after a response limit, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/fillout/forms. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/fillout/forms with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Fillout.

### list_forms

Forms in your Fillout account with their IDs and names. Access: read. REST: `GET /api/v1/fillout/forms`. MCP: `fillout_read → list_forms`.

No parameters.

Returns every form your account can see, each with the form ID and its name. Use form_id from each item as the form_id parameter of the other tools.

Example response:

```json
{
  "forms": [
    {
      "form_id": "fpj3Kd9xQw2L",
      "name": "Webinar registration"
    },
    {
      "form_id": "rK8mTn4vYb1C",
      "name": "Discount application"
    },
    {
      "form_id": "tD6wNs3hLz8P",
      "name": "Autumn event"
    }
  ]
}
```

### get_form

A form's questions with ID and field type, plus calculations and URL parameters. Access: read. REST: `GET /api/v1/fillout/forms/{form_id}`. MCP: `fillout_read → get_form`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |

Returns the questions of one form in page order, each with its ID, label and field type, together with calculations, URL parameters and any quiz, scheduling or payment fields. Use the question IDs in update_question and set_question_logic. Logic is not part of this result; get_form_logic returns it.

Example response:

```json
{
  "form_id": "fpj3Kd9xQw2L",
  "name": "Webinar registration",
  "questions": [
    {
      "id": "q_full_name",
      "name": "Full name",
      "type": "ShortAnswer"
    },
    {
      "id": "q_work_email",
      "name": "Work email",
      "type": "EmailInput"
    },
    {
      "id": "q_company_size",
      "name": "Company size",
      "type": "Dropdown"
    },
    {
      "id": "q_learn",
      "name": "What do you want to learn?",
      "type": "LongAnswer"
    }
  ],
  "calculations": [],
  "url_parameters": [
    {
      "id": "utm_source",
      "name": "utm_source"
    }
  ]
}
```

### get_form_logic

Show and hide rules on questions and the branches between pages. Access: read. REST: `GET /api/v1/fillout/forms/{form_id}/logic`. MCP: `fillout_read → get_form_logic`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |

Returns the conditions set on each question (hide when, hide always) and the page branches from the Logic view, each with its condition and target page. Read it before changing logic so a new rule does not collide with an old one.

Example response:

```json
{
  "form_id": "rK8mTn4vYb1C",
  "question_rules": [
    {
      "question_id": "q_org_description",
      "hide_always": false,
      "hide_when": [
        {
          "source": "answer",
          "question_id": "q_company_type",
          "operator": "is not",
          "value": "Non-profit"
        }
      ]
    }
  ],
  "page_branches": [
    {
      "from_page": "Info",
      "to_page": "Accepted",
      "condition": {
        "question_id": "q_company_type",
        "operator": "is",
        "value": "Student"
      }
    }
  ]
}
```

### list_submissions

Submissions of a form with their answers, filtered by date, status or text. Access: read. REST: `GET /api/v1/fillout/forms/{form_id}/submissions`. MCP: `fillout_read → list_submissions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `status` | enum | no | finished or in_progress. Default: finished. In-progress submissions are unfinished ones. |
| `after_date` | datetime | no | Only submissions made after this time. |
| `before_date` | datetime | no | Only submissions made before this time. |
| `search` | string | no | Only submissions containing this text. |
| `sort` | enum | no | asc or desc. Default: asc. |
| `include_preview` | boolean | no | Also return submissions made in Preview mode. |
| `limit` | integer | no | 1 to 150. Default: 50. |
| `offset` | integer | no | Start position in the list. Default: 0. |

Returns the submissions of one form with every answer, in the order set by sort (oldest first by default). Only finished submissions come back unless status is in_progress. Pages hold up to 150 submissions; the call also returns total_responses and page_count for the filter, so you can page with offset. Test submissions made in Preview are left out unless include_preview is true.

Example response:

```json
{
  "submissions": [
    {
      "submission_id": "sb_71f3a9",
      "submitted_at": "2026-10-12T09:41:00Z",
      "answers": [
        {
          "question": "Full name",
          "value": "Ana Lopez"
        },
        {
          "question": "Work email",
          "value": "ana@acme.example"
        }
      ]
    }
  ],
  "total_responses": 38,
  "page_count": 1
}
```

### get_submission

One submission with all its answers, calculations and URL parameters. Access: read. REST: `GET /api/v1/fillout/forms/{form_id}/submissions/{submission_id}`. MCP: `fillout_read → get_submission`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `submission_id` | string | yes | Submission ID from list_submissions. |
| `include_edit_link` | boolean | no | Add the link to edit the submission. |

Returns one submission by ID with every answer, calculation result and URL parameter value. Set include_edit_link to get the link where the submission can be edited.

Example response:

```json
{
  "submission_id": "sb_71f3a9",
  "submitted_at": "2026-10-12T09:41:00Z",
  "answers": [
    {
      "question": "Full name",
      "value": "Ana Lopez"
    },
    {
      "question": "Work email",
      "value": "ana@acme.example"
    },
    {
      "question": "Company size",
      "value": "11-50"
    }
  ],
  "url_parameters": [
    {
      "name": "utm_source",
      "value": "newsletter"
    }
  ],
  "edit_link": "https://forms.fillout.com/edit/sb_71f3a9"
}
```

### get_form_settings

Access settings and email notifications of a form. Access: read. REST: `GET /api/v1/fillout/forms/{form_id}/settings`. MCP: `fillout_read → get_form_settings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |

Returns the Access settings of one form (closed, open date, expiration date, submission limit, closed message) and its self-email notifications. Use it before update_form_access or set_email_notifications to see what is set now.

Example response:

```json
{
  "form_id": "tD6wNs3hLz8P",
  "access": {
    "closed": false,
    "open_date": null,
    "expiration_date": "2026-11-15T23:59:00+01:00",
    "submission_limit": null,
    "closed_message": null
  },
  "self_email_notifications": {
    "enabled": true,
    "emails": [
      "events@acme.example"
    ]
  }
}
```

### create_form

Create a new form with a name and its questions, not yet published. Access: write. REST: `POST /api/v1/fillout/forms`. MCP: `fillout_write → create_form`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Form name. |
| `questions` | array | yes | Questions in order. Each item: label (required), type (Address, AudioRecording, Calcom, Calendly, Captcha, Checkbox, Checkboxes, ColorPicker, CurrencyInput, DatePicker, DateRange, DateTimePicker, Dropdown, EmailInput, FileUpload, ImagePicker, LocationCoordinates, LongAnswer, Matrix, MultiSelect, MultipleChoice, NumberInput, OpinionScale, Password, Payment, PhoneNumber, Ranking, RecordPicker, ShortAnswer, Signature, Slider, StarRating, Subform, SubmissionPicker, Switch, Table, TimePicker or URLInput. Default: ShortAnswer) and options (array of strings, for choice types). |

Creates a form with one question per entry, in the order given, and returns its ID and the questions with their types. A question without a type becomes ShortAnswer; options are for Dropdown, MultipleChoice and Checkboxes. The form is not published, so no respondent can reach it before publish_form. This call reaches no one and is undone by deleting the form in the dashboard, so it runs without asking first.

Example response:

```json
{
  "form_id": "fpj3Kd9xQw2L",
  "name": "Webinar registration",
  "published": false,
  "questions": [
    {
      "id": "q_full_name",
      "name": "Full name",
      "type": "ShortAnswer"
    },
    {
      "id": "q_work_email",
      "name": "Work email",
      "type": "EmailInput"
    },
    {
      "id": "q_company_size",
      "name": "Company size",
      "type": "Dropdown"
    },
    {
      "id": "q_learn",
      "name": "What do you want to learn?",
      "type": "LongAnswer"
    }
  ]
}
```

### add_question

Add one question of any field type to a form. Access: write. REST: `POST /api/v1/fillout/forms/{form_id}/questions`. MCP: `fillout_write → add_question`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `label` | string | yes | The question text. |
| `type` | enum | yes | Field type: Address, AudioRecording, Calcom, Calendly, Captcha, Checkbox, Checkboxes, ColorPicker, CurrencyInput, DatePicker, DateRange, DateTimePicker, Dropdown, EmailInput, FileUpload, ImagePicker, LocationCoordinates, LongAnswer, Matrix, MultiSelect, MultipleChoice, NumberInput, OpinionScale, Password, Payment, PhoneNumber, Ranking, RecordPicker, ShortAnswer, Signature, Slider, StarRating, Subform, SubmissionPicker, Switch, Table, TimePicker or URLInput. |
| `options` | array | no | Answer options, for Dropdown, MultipleChoice, Checkboxes and similar types. |
| `required` | boolean | no | Make the question required. Default: false. |
| `page` | string | no | Name of the form page to add it to. Default: the last form page. |

Adds a question to a page of a form and returns its ID. Use it for fields that need more than a label, such as a signature, a file upload or a rating. Choice types take options. The change reaches respondents only after publish_form. This call is undone by update_question or by restoring an earlier version from the editor's edit history, so it runs without asking first.

Example response:

```json
{
  "form_id": "fpj3Kd9xQw2L",
  "question": {
    "id": "q_rating",
    "name": "How was the session?",
    "type": "StarRating",
    "required": false
  }
}
```

### update_question

Change a question's label, type, options or whether it is required. Access: write. REST: `PATCH /api/v1/fillout/forms/{form_id}/questions/{question_id}`. MCP: `fillout_write → update_question`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `question_id` | string | yes | Question ID from get_form. |
| `label` | string | no | New question text. |
| `type` | enum | no | New field type: Address, AudioRecording, Calcom, Calendly, Captcha, Checkbox, Checkboxes, ColorPicker, CurrencyInput, DatePicker, DateRange, DateTimePicker, Dropdown, EmailInput, FileUpload, ImagePicker, LocationCoordinates, LongAnswer, Matrix, MultiSelect, MultipleChoice, NumberInput, OpinionScale, Password, Payment, PhoneNumber, Ranking, RecordPicker, ShortAnswer, Signature, Slider, StarRating, Subform, SubmissionPicker, Switch, Table, TimePicker or URLInput. |
| `options` | array | no | Replaces the answer options. |
| `required` | boolean | no | Make the question required or optional. |

Changes one question of a form and returns it as it is now. Only the fields you pass are changed. The change reaches respondents only after publish_form. Changing the type of a question that already has answers can hide them in Results, so check get_form and list_submissions first. This call is undone by the editor's edit history, so it runs without asking first.

Example response:

```json
{
  "form_id": "fpj3Kd9xQw2L",
  "question": {
    "id": "q_company_size",
    "name": "Company size",
    "type": "Dropdown",
    "required": true
  }
}
```

### set_question_logic

Hide a question when conditions are met, or always. Access: write. REST: `PUT /api/v1/fillout/forms/{form_id}/questions/{question_id}/logic`. MCP: `fillout_write → set_question_logic`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `question_id` | string | yes | Question ID from get_form. |
| `hide_when` | array | no | Conditions as in the editor's Add condition. Each item: source (answer or url_parameter), question_id or name, operator (as the condition editor offers it for that field), value. |
| `hide_always` | boolean | no | Always hide the question. Default: false. |

Sets the Logic of one question: hide_when conditions on earlier answers or URL parameters, or hide_always for a field that only carries a pre-filled value. It replaces the conditions the question had. Conditions that depend on integration data are not set by this tool. The change reaches respondents only after publish_form, and it is undone by the editor's edit history, so it runs without asking first.

Example response:

```json
{
  "form_id": "rK8mTn4vYb1C",
  "question_id": "q_org_description",
  "hide_always": false,
  "hide_when": [
    {
      "source": "answer",
      "question_id": "q_company_type",
      "operator": "is not",
      "value": "Non-profit"
    }
  ]
}
```

### set_page_branch

Route respondents from one page to another when a condition is met. Access: write. REST: `PUT /api/v1/fillout/forms/{form_id}/page-branch`. MCP: `fillout_write → set_page_branch`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `from_page` | string | yes | Name of the page respondents leave. |
| `to_page` | string | yes | Name of the page, or ending page, they go to. |
| `condition` | object | no | Branch condition: question_id, operator (as the condition editor offers it for that field), value. Empty means the default path. |

Adds a branch from one form page to another, with a condition on an earlier answer, the same as dragging a connector in the Logic view. Leave condition empty to set the default path. Page names come from get_form_logic. The change reaches respondents only after publish_form, and it is undone by the editor's edit history, so it runs without asking first.

Example response:

```json
{
  "form_id": "rK8mTn4vYb1C",
  "branch": {
    "from_page": "Info",
    "to_page": "Accepted",
    "condition": {
      "question_id": "q_company_type",
      "operator": "is",
      "value": "Student"
    }
  }
}
```

### update_form_access

Close a form, set open and expiration dates, a submission limit or a closed message. Access: write, asks the user first. REST: `PATCH /api/v1/fillout/forms/{form_id}/access`. MCP: `fillout_write → update_form_access`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `closed` | boolean | no | true closes the form now, false reopens it. |
| `open_date` | datetime | no | When the form starts accepting responses. |
| `expiration_date` | datetime | no | When the form stops accepting responses. |
| `submission_limit` | integer | no | Close the form after this many responses. |
| `closed_message` | string | no | Message shown when the form is closed. |

Changes the Access settings of one form: Close form, Form open date, Form expiration date, Form submission limit and Custom form closed message. Only the fields you pass change; pass null to clear one. Closing a form stops new submissions at once, so respondents see the closed message. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": "tD6wNs3hLz8P",
  "access": {
    "closed": false,
    "open_date": null,
    "expiration_date": "2026-11-30T23:59:00+01:00",
    "submission_limit": null,
    "closed_message": "Registration is closed. See you next year."
  }
}
```

### set_email_notifications

Turn self-email notifications on a form on or off and set who gets them. Access: write, asks the user first. REST: `PUT /api/v1/fillout/forms/{form_id}/email-notifications`. MCP: `fillout_write → set_email_notifications`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `enabled` | boolean | yes | Turn notifications on or off. |
| `emails` | array | no | Addresses that get a message on each submission. |

Sets the Self-email notifications of one form: on or off, and the emails that receive a message each time someone submits. Two or more addresses are allowed. On a Free plan, an organization created on or after 5 October 2026 sends notifications only to its own members until the account is verified. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": "tD6wNs3hLz8P",
  "self_email_notifications": {
    "enabled": true,
    "emails": [
      "events@acme.example",
      "sam@acme.example"
    ]
  }
}
```

### publish_form

Publish a form so respondents can fill it in, with every change made since the last publish. Access: write, asks the user first. REST: `POST /api/v1/fillout/forms/{form_id}/publish`. MCP: `fillout_write → publish_form`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `responses_go_to` | enum | no | First publish only: new_database, existing_database or just_this_form. Default: just_this_form. |

Publishes the form, which makes every unpublished change visible to respondents. On the first publish, responses_go_to sets where responses are saved: a new Zite database, a table in an existing database, or only the form's Results. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": "fpj3Kd9xQw2L",
  "published": true,
  "responses_go_to": "just_this_form"
}
```

### delete_submission

Delete one submission permanently, with its uploaded files. Access: write, asks the user first. REST: `DELETE /api/v1/fillout/forms/{form_id}/submissions/{submission_id}`. MCP: `fillout_write → delete_submission`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `submission_id` | string | yes | Submission ID from list_submissions. |

Deletes one submission from a form's Results. The deletion is permanent and cannot be undone, and it also deletes the file uploads of that submission. Files already sent to tools like Airtable stay there. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": "fpj3Kd9xQw2L",
  "submission_id": "sb_71f3a9",
  "status": "deleted"
}
```

## How do I connect Fillout to Claude Code, Codex or Cursor?

Connecting Fillout takes three steps: sign up, sign in to Fillout once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Fillout to your agent.

1. **Create an account** Sign up and add Fillout in the console. Your API key is there too.

2. **Sign in to Fillout in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Fillout there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Fillout tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Build a Fillout form called "Webinar registration" with four questions: full name, work email, company size as a dropdown (1-10, 11-50, 51+) and what they want to learn. Read it back to me, then publish it with responses saved only in the form.
```

### Call Fillout from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/fillout with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X PATCH https://cotlet.dev/api/v1/fillout/forms/tD6wNs3hLz8P/access \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"expiration_date":"2026-11-30T23:59:00+01:00","closed_message":"Registration is closed. See you next year."}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "form_id": "tD6wNs3hLz8P",
  "access": {
    "closed": false,
    "open_date": null,
    "expiration_date": "2026-11-30T23:59:00+01:00",
    "submission_limit": null,
    "closed_message": "Registration is closed. See you next year."
  }
}
```

## Why use Cotlet for Fillout?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Fillout yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Fillout changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Fillout to Cotlet?

Yes. You sign in to Fillout yourself, in your own Cloud Browser, and we never save your password. Your agents only get Fillout once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Fillout integration?**

No, Cotlet is independent of Fillout. Fillout's own API is too limited for this work. Cotlet works through your own Fillout account, the way you use Fillout in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Fillout in your console: your agents lose access at once and you stay signed in. Signing out of Fillout in the browser works too, and Reset browser deletes the whole profile.

## Is there a Fillout MCP server on GitHub?

Yes. Community Fillout MCP servers exist on GitHub, usually maintained by one person. You install one yourself and give it a Fillout API key. They wrap the REST API, so they read forms and submissions but cannot build a form. Cotlet hosts the same kind of server for you, works in the editor as you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create an API key in Developer settings, add the server to each MCP client | Sign up, sign in to Fillout once, add one MCP server or API key |
| What it can do | What the REST API offers: forms, questions, submissions and webhooks. It cannot create or edit a form | Also builds forms: questions, logic, access settings and publishing, the way you do in the editor |
| When Fillout changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Fillout access | An API key in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail when you revoke or regenerate the key, until you update it by hand | Your Cloud Browser keeps you signed in; if Fillout logs you out, your agent gets a link to sign in again |
| Where it runs | Your computer, while it is on; you update and debug it yourself | Hosted, nothing to update: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Fillout changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Fillout API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Fillout API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Fillout account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Fillout yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Fillout only after you enable it. When Fillout signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Fillout, sign out of Fillout in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Fillout's terms:** You use your own Fillout account and stay responsible for following Fillout's terms. Cotlet is independent and not affiliated with Fillout. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Fillout in the console and press Request access. Then you create your API key and connect Fillout there.

**Do I need to be technical?**

No. You sign in to Fillout once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Fillout to Cotlet?**

Yes. You sign in to Fillout yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Fillout once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Fillout sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Fillout cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Fillout's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Fillout sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Fillout login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Fillout offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need an API key or a paid Fillout plan?**

No API key. Cotlet works in your signed-in Fillout account, so the key from Developer settings is not used. Fillout's help pages do not state which plan the REST API needs. What your agent can do follows your role: a Member edits only their own forms, and an Admin has full access to the workspace.

**Can my agent edit a form while a teammate has it open?**

Fillout says collaborators cannot edit the same form at the same time, but can edit different forms at once. Ask your agent to work on forms nobody has open, or on a duplicate.

**Can my agent post or send messages in Fillout without asking me?**

No. Every call to update_form_access, set_email_notifications, publish_form or delete_submission waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_form, add_question, update_question, set_question_logic, set_page_branch runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Fillout API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/fillout from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.