[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)

# 123FormBuilder API and MCP server

> 123FormBuilder has a REST API v2 with token login (checked 23 Oct 2026). It lists, creates, renames and deletes forms, reads form fields, reads and deletes submissions, and manages groups and subusers. It cannot add or change form fields, edit what a respondent submitted, change notification emails or resend one, and there is no official MCP server.

Online form builder: you build forms in a drag-and-drop editor, publish them by link or embed, collect submissions and send notification emails.

## What is the 123FormBuilder API?

Cotlet's 123FormBuilder API exposes 14 endpoints for your own 123FormBuilder account: list forms, get form, list submissions, get submission, list notification emails, get publish links, update submission, resend submission, delete submission, update notification email, add form field, update form field, activate or deactivate form and duplicate form. The list_forms endpoint returns forms of your account with id, name, state, folder and submission counts. Each endpoint takes simple JSON inputs like form_id, submission_id or cursor and works both as an operation of the 123formbuilder_read or 123formbuilder_write MCP tool for agents and as a REST call for scripts.

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

123FormBuilder has a REST API v2 with token login (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for 123FormBuilder with 14 endpoints (6 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does 123FormBuilder have an official API?

123FormBuilder has a REST API v2 with token login (checked 23 Oct 2026). It lists, creates, renames and deletes forms, reads form fields, reads and deletes submissions, and manages groups and subusers. It cannot add or change form fields, edit what a respondent submitted, change notification emails or resend one, and there is no official MCP server.

| Task | 123FormBuilder official | Cotlet |
|---|---|---|
| List forms and read submissions | Yes: GET /forms and GET /forms/{form_id}/submissions | Yes |
| Delete a submission | Yes: DELETE /forms/{form_id}/submissions/{submission_id} | Yes |
| Duplicate a form | Partly: The API creates a new form with a name; it has no duplicate call and no way to fill it with fields | Yes |
| Deactivate or reactivate a form | Yes: PUT /forms/{form_id} with the active setting | Yes |
| Add or change form fields | No: GET /forms/{form_id}/fields only reads them | Yes |
| Edit what a respondent submitted | No: Update Submission changes only the payment and approval status | Yes |
| Change notification emails | No | Yes |
| Resend a submission email | No | Yes |

Sources: [123FormBuilder Developer Center: API v2](https://www.123formbuilder.com/developer/api-v2/), [123FormBuilder Developer Center: API v2 Forms (Swagger reference)](https://www.123formbuilder.com/developer/api-v2-forms/), [Help: How many API calls can I use?](https://www.123formbuilder.com/docs/how-many-api-calls-can-i-use/), [Zapier: 123FormBuilder integrations](https://zapier.com/apps/123formbuilder/integrations)

## Quick reference

```text
123FormBuilder has a REST API v2 with token login (checked 23 Oct 2026). It lists, creates, renames and deletes forms, reads form fields, reads and deletes submissions, and manages groups and subusers. It cannot add or change form fields, edit what a respondent submitted, change notification emails or resend one, and there is no official MCP server.
Cotlet provides a hosted MCP server and REST API for 123FormBuilder: 14 tools (6 read, 8 write).
Access       Sign up at https://cotlet.dev/app/signup?app=123formbuilder, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    123formbuilder_read, 123formbuilder_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/123formbuilder, each operation at its own route, e.g. PATCH /api/v1/123formbuilder/forms/{form_id}/notification-email
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, list_submissions, get_submission, list_notification_emails, get_publish_links, update_submission, resend_submission, delete_submission, update_notification_email, add_form_field, update_form_field, set_form_active, duplicate_form
Confirm      update_submission, resend_submission, delete_submission, update_notification_email, add_form_field, update_form_field, set_form_active (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/123formbuilder-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=123formbuilder, requests 123FormBuilder in the Cotlet console and creates an API key there.
2. The user signs in to 123FormBuilder once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables 123FormBuilder 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 123FormBuilder server that someone else maintains, including non-developers.

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 123FormBuilder 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 123FormBuilder 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 123FormBuilder 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 123FormBuilder's terms; Cotlet is not affiliated with 123FormBuilder.
```

## What can an AI agent do in 123FormBuilder?

Cotlet is best for 123FormBuilder owners and operations teams who need an AI agent to fix entries, reroute notification emails and edit forms without running or fixing a server.

- **[Correct a submission and resend it](https://cotlet.dev/integrations/123formbuilder-api-mcp-server/correct-a-submission-and-resend.md)**: "In the Contact us form, change the phone number in Ana Lopez's latest submission to 555 0143, then resend it to my inbox." → `list_submissions`, `get_submission`, `update_submission`, `resend_submission`
- **[Change notification recipients on many forms](https://cotlet.dev/integrations/123formbuilder-api-mcp-server/change-notification-recipients.md)**: "List every form with a notification email that goes to jan@yourcompany.com and send it to ops@yourcompany.com instead. Show me the list first." → `list_forms`, `list_notification_emails`, `update_notification_email`
- **[Duplicate a form and change its fields](https://cotlet.dev/integrations/123formbuilder-api-mcp-server/duplicate-form-and-edit-fields.md)**: "Duplicate the Spring open day form as Autumn open day, add a Work email field and change the instructions of the Phone field to "Include the country code"." → `list_forms`, `duplicate_form`, `get_form`, `add_form_field`, `update_form_field`, `get_publish_links`
- **Daily digest of new submissions** (runs: daily): "Every morning, list the forms that got new submissions in the last 24 hours and summarise what people asked in each one." → `list_forms`, `list_submissions`
- **Delete test submissions**: "In the Contact us form, find the submissions where the name is Test or the email ends in @example.com and show them to me before deleting." → `list_submissions`, `delete_submission`

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

Yes. Cotlet does not replace your automation platform: it gives it a 123FormBuilder 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 daily digest of new submissions, 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/123formbuilder/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/123formbuilder/forms with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 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 123FormBuilder.

### list_forms

Forms of your account with id, name, state, folder and submission counts. Access: read. REST: `GET /api/v1/123formbuilder/forms`. MCP: `123formbuilder_read → list_forms`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Keep forms whose name contains this text. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the forms you see in My Forms, with the form id (the ID in the form's menu), whether the form is active, its folder and the number of submissions. new_last_24h is the count the app marks in the orange badge. search keeps forms whose name contains the text. Pass next_cursor back as cursor to read more.

Example response:

```json
{
  "forms": [
    {
      "form_id": 5128403,
      "name": "Contact us",
      "active": true,
      "folder": "Website",
      "submissions": 214,
      "new_last_24h": 3
    },
    {
      "form_id": 5128977,
      "name": "Spring open day",
      "active": true,
      "folder": "Events",
      "submissions": 96,
      "new_last_24h": 7
    }
  ],
  "next_cursor": null
}
```

### get_form

One form with its fields in order: label, type, required and instructions. Access: read. REST: `GET /api/v1/123formbuilder/forms/{form_id}`. MCP: `123formbuilder_read → get_form`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | integer | yes | Form id from list_forms. |

Opens the form in the Form Editor and returns its fields from top to bottom with their label, field type as named in the Fields panel, whether they are required and the text in the Instructions box. Use the labels with update_submission and add_form_field.

Example response:

```json
{
  "form_id": 5128977,
  "name": "Spring open day",
  "fields": [
    {
      "label": "Full name",
      "type": "Name",
      "required": true,
      "instructions": ""
    },
    {
      "label": "Email",
      "type": "Email",
      "required": true,
      "instructions": "We send the confirmation here"
    },
    {
      "label": "Phone",
      "type": "Phone",
      "required": false,
      "instructions": ""
    }
  ]
}
```

### list_submissions

Submissions of a form with their answers, optionally from a date on. Access: read. REST: `GET /api/v1/123formbuilder/forms/{form_id}/submissions`. MCP: `123formbuilder_read → list_submissions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | integer | yes | Form id from list_forms. |
| `since` | date | no | Only entries received on or after this date. |
| `cursor` | string | no | Next page cursor from the previous call. |

Reads the Submissions tab under Results, entry by entry, in the order the tab shows them. Each entry has its id, the time it arrived and its answers by field label. since keeps entries from that date on. Pass next_cursor back as cursor to continue. The call does not change the read state of an entry.

Example response:

```json
{
  "submissions": [
    {
      "submission_id": 91827364,
      "received_at": "2026-10-21T09:12:00Z",
      "answers": {
        "Full name": "Ana Lopez",
        "Email": "ana@example.com",
        "Phone": "555 0142"
      }
    },
    {
      "submission_id": 91827301,
      "received_at": "2026-10-20T16:40:00Z",
      "answers": {
        "Full name": "Tom Becker",
        "Email": "tom@example.com",
        "Phone": ""
      }
    }
  ],
  "next_cursor": null
}
```

### get_submission

One submission with all its answers. Access: read. REST: `GET /api/v1/123formbuilder/forms/{form_id}/submissions/{submission_id}`. MCP: `123formbuilder_read → get_submission`.

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

Opens one entry from the Submissions tab and returns all its answers by field label. Files uploaded with the form are returned as names, not as content. Use it before update_submission to see the exact old values.

Example response:

```json
{
  "submission_id": 91827364,
  "form_id": 5128403,
  "received_at": "2026-10-21T09:12:00Z",
  "answers": {
    "Full name": "Ana Lopez",
    "Email": "ana@example.com",
    "Phone": "555 0142",
    "Message": "Do you offer a weekend slot?"
  }
}
```

### list_notification_emails

The emails a form sends on submit: name, recipients, subject and rules. Access: read. REST: `GET /api/v1/123formbuilder/forms/{form_id}/notification-emails`. MCP: `123formbuilder_read → list_notification_emails`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | integer | yes | Form id from list_forms. |

Reads the Emails section of a form. Each email has its name, whether it is on, the Send to addresses, the subject and any Add rules conditions as text. Pass email_id to update_notification_email. A new form has a default email sent to the account email address.

Example response:

```json
{
  "form_id": 5128403,
  "emails": [
    {
      "email_id": "default",
      "name": "Default notification",
      "enabled": true,
      "send_to": [
        "jan@yourcompany.com"
      ],
      "subject": "New submission: Contact us",
      "rules": "All Submissions"
    },
    {
      "email_id": "autoresponder",
      "name": "Autoresponder",
      "enabled": true,
      "send_to": [
        "Email field: Email"
      ],
      "subject": "We got your message",
      "rules": "All Submissions"
    }
  ]
}
```

### get_publish_links

The link to a form and its JavaScript embed code. Access: read. REST: `GET /api/v1/123formbuilder/forms/{form_id}/publish-links`. MCP: `123formbuilder_read → get_publish_links`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | integer | yes | Form id from list_forms. |

Reads the Publish section: the link to the form and the JavaScript code from the Embed form tab. The embed code stays valid when you edit the form later, because the page loads the current form. It returns text only and publishes nothing.

Example response:

```json
{
  "form_id": 5130021,
  "link": "https://form.123formbuilder.com/5130021/autumn-open-day",
  "embed_javascript": "<script>/* JavaScript embed code of the form */</script>"
}
```

### update_submission

Change answers in a submission, like Edit and Update Submission in Results. Access: write, asks the user first. REST: `PATCH /api/v1/123formbuilder/forms/{form_id}/submissions/{submission_id}`. MCP: `123formbuilder_write → update_submission`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | integer | yes | Form id from list_forms. |
| `submission_id` | integer | yes | Submission id from list_submissions. |
| `values` | object | yes | Field label to new value, for the fields you change. |

Edits the data a respondent provided, field by field, and saves it. Fields you leave out stay as they are; a label that is not on the form fails. The default report updates by itself, custom reports need an Update click in the app. Respondents are not told by default. If the form resends notifications on edit, the app sends them when the entry is saved, and notifications_resent is true. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "submission_id": 91827364,
  "form_id": 5128403,
  "changed": [
    {
      "field": "Phone",
      "old": "555 0142",
      "new": "555 0143"
    }
  ],
  "notifications_resent": false
}
```

### resend_submission

Send a submission to your inbox again with one of the form's email templates. Access: write, asks the user first. REST: `POST /api/v1/123formbuilder/forms/{form_id}/submissions/{submission_id}/resend`. MCP: `123formbuilder_write → resend_submission`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | integer | yes | Form id from list_forms. |
| `submission_id` | integer | yes | Submission id from list_submissions. |
| `email_id` | string | yes | Email id from list_notification_emails. |

Uses Resend on an entry in Results. The email goes out with the template you name from the form's emails, to that email's recipients. A template that does not exist on the form fails and lists the available names. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "submission_id": 91827364,
  "email_id": "default",
  "sent_to": [
    "ops@yourcompany.com"
  ],
  "status": "sent"
}
```

### delete_submission

Delete one submission from the Submissions tab. Access: write, asks the user first. REST: `DELETE /api/v1/123formbuilder/forms/{form_id}/submissions/{submission_id}`. MCP: `123formbuilder_write → delete_submission`.

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

Checks the entry and deletes it, like Delete in Results. 123FormBuilder says its support can restore deleted entries within 30 days; this tool has no undo. Product stock levels are not updated. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "submission_id": 91827301,
  "form_id": 5128403,
  "deleted": true
}
```

### update_notification_email

Change Send to and the subject of one email a form sends. Access: write, asks the user first. REST: `PATCH /api/v1/123formbuilder/forms/{form_id}/notification-email`. MCP: `123formbuilder_write → update_notification_email`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | integer | yes | Form id from list_forms. |
| `email_id` | string | yes | Email id from list_notification_emails. |
| `send_to` | array | no | Email addresses that replace the typed ones in Send to. |
| `subject` | string | no | New subject. Field variables are allowed. |

Edits one email in the Emails section. send_to replaces the typed addresses; the account email, email fields of the form and Add rules conditions stay as they are. The body and sender are not touched. From the next submission on, the new recipients get the email. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": 5128403,
  "email_id": "default",
  "name": "Default notification",
  "enabled": true,
  "send_to": [
    "ops@yourcompany.com"
  ],
  "subject": "New submission: Contact us"
}
```

### add_form_field

Add a field to a form in the Form Editor. Access: write, asks the user first. REST: `POST /api/v1/123formbuilder/forms/{form_id}/field`. MCP: `123formbuilder_write → add_form_field`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | integer | yes | Form id from list_forms. |
| `field_type` | string | yes | Field type as named in the Fields panel, e.g. Email. |
| `label` | string | yes | Label shown above the field. |
| `after_field` | string | no | Label of the field it goes below. |

Adds one field by the name it has in the Fields panel (Essentials, Contact details, Date & Time and the other groups). With after_field it is placed below that field, like a field added while another is selected; without it, at the end. A form embedded with the JavaScript code shows the new field as soon as it is saved. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": 5130021,
  "field": {
    "label": "Work email",
    "type": "Email",
    "required": false
  },
  "position": 3
}
```

### update_form_field

Change the label or the instructions of a field. Access: write, asks the user first. REST: `PATCH /api/v1/123formbuilder/forms/{form_id}/field`. MCP: `123formbuilder_write → update_form_field`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | integer | yes | Form id from list_forms. |
| `field` | string | yes | Current label of the field, from get_form. |
| `label` | string | no | New label. |
| `instructions` | string | no | New text for the Instructions box. |

Selects a field by its label and changes its label or the text in the Instructions box under Quick setup. Fields you do not name stay as they are. Answers already collected keep working. A form embedded with the JavaScript code shows the change as soon as it is saved. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": 5130021,
  "field": {
    "label": "Phone",
    "type": "Phone",
    "instructions": "Include the country code"
  }
}
```

### set_form_active

Turn a form on or off, like Deactivate in My Forms. Access: write, asks the user first. REST: `PUT /api/v1/123formbuilder/forms/{form_id}/active`. MCP: `123formbuilder_write → set_form_active`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | integer | yes | Form id from list_forms. |
| `active` | boolean | yes | true to turn the form on, false to deactivate it. |

Switches the form on or off. A deactivated form stops taking submissions from the public and still counts toward your form limit. Scheduling dates set in Schedule are not changed. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": 5128977,
  "name": "Spring open day",
  "active": false
}
```

### duplicate_form

Copy a form with all its settings, optionally under a new name. Access: write. REST: `POST /api/v1/123formbuilder/forms/{form_id}/duplicate`. MCP: `123formbuilder_write → duplicate_form`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | integer | yes | Form id of the form to copy, from list_forms. |
| `name` | string | no | Name of the copy. |

Uses Duplicate in the form's menu in My Forms, which copies the form with all its settings, then renames the copy if you pass name. The copy counts toward your form limit. It reaches no one and you undo it by deleting the copy in the app, so it does not wait for your OK.

Example response:

```json
{
  "source_form_id": 5128977,
  "form_id": 5130021,
  "name": "Autumn open day",
  "active": true
}
```

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

Connecting 123FormBuilder takes three steps: sign up, sign in to 123FormBuilder 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 123FormBuilder to your agent.

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

2. **Sign in to 123FormBuilder in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to 123FormBuilder 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 123FormBuilder 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.

```
In the Contact us form, change the phone number in Ana Lopez's latest submission to 555 0143, then resend it to my inbox.
```

### Call 123FormBuilder 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/123formbuilder 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/123formbuilder/forms/5128403/notification-email \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email_id":"default","send_to":["ops@yourcompany.com"],"subject":"New submission: Contact us"}'
```

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

```
{
  "form_id": 5128403,
  "email_id": "default",
  "name": "Default notification",
  "enabled": true,
  "send_to": [
    "ops@yourcompany.com"
  ],
  "subject": "New submission: Contact us"
}
```

## Why use Cotlet for 123FormBuilder?

**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 123FormBuilder 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 123FormBuilder changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect 123FormBuilder to Cotlet?

Yes. You sign in to 123FormBuilder yourself, in your own Cloud Browser, and we never save your password. Your agents only get 123FormBuilder 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 123FormBuilder integration?**

No, Cotlet is independent of 123FormBuilder. 123FormBuilder's own API is too limited for this work. Cotlet works through your own 123FormBuilder account, the way you use 123FormBuilder 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 123FormBuilder in your console: your agents lose access at once and you stay signed in. Signing out of 123FormBuilder in the browser works too, and Reset browser deletes the whole profile.

## Is there a 123FormBuilder MCP server on GitHub?

No community 123FormBuilder MCP server turned up on GitHub (checked 23 Oct 2026). The usual option is Zapier or Make. Zapier's 123FormBuilder app has two triggers, New Form and New Submission, and no actions. Make has two Watch triggers and one Make an API Call module, so it reaches only what API v2 offers. Cotlet works in the signed-in app, so it also covers fields, submission edits and notification emails, and it adds an MCP server for your agent.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Connect your 123FormBuilder account, then pick a trigger | Sign up, sign in to 123FormBuilder once, add one MCP server or API key |
| What it can do | Starts a Zap on a new form or a new submission; no actions of its own | Reads forms and submissions, edits and deletes entries, changes notification emails, adds and edits form fields |
| API calls | Each sync uses API calls; the free 123FormBuilder plan allows 100 a day | Works in the signed-in app, so the daily API call limit does not apply |
| When the app changes | Zapier maintains its app | Our team tests it daily and fixes it for you; failed calls are free |
| Your session | A connection to your account stored by Zapier | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| Where it runs | Inside Zapier | Hosted: Claude Code, Codex, Cursor, n8n, Make, Zapier and scripts, also on a schedule |
| Price | Your Zapier plan | 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 123FormBuilder 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 123FormBuilder API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the 123FormBuilder 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 10 credits (about $0.04 to $0.06), 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 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $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 123FormBuilder 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 123FormBuilder 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 123FormBuilder only after you enable it. When 123FormBuilder 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 123FormBuilder, sign out of 123FormBuilder 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.
- **123FormBuilder's terms:** You use your own 123FormBuilder account and stay responsible for following 123FormBuilder's terms. Cotlet is independent and not affiliated with 123FormBuilder. [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 123FormBuilder in the console and press Request access. Then you create your API key and connect 123FormBuilder there.

**Do I need to be technical?**

No. You sign in to 123FormBuilder 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 123FormBuilder to Cotlet?**

Yes. You sign in to 123FormBuilder yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get 123FormBuilder 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 123FormBuilder 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 123FormBuilder 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 123FormBuilder's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. 123FormBuilder 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 123FormBuilder 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?**

123FormBuilder 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).

**Does the 123FormBuilder API work on the free plan?**

Yes, with a daily cap. 123FormBuilder says the free Basic plan allows up to 100 API calls a day and paid plans have unlimited calls. Integrations such as Zapier use calls on every sync. Cotlet works in the signed-in app, not through the API, so that cap does not apply to it.

**Can a deleted submission be restored?**

123FormBuilder says its support can restore deleted entries within 30 days. Cotlet has no undo for delete_submission, so each delete waits for your OK by default.

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

No. Every call to update_submission, resend_submission, delete_submission, update_notification_email, add_form_field, update_form_field or set_form_active waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. duplicate_form runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the 123FormBuilder 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/123formbuilder 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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.