123FormBuilder automation
Change 123FormBuilder notification recipients on many forms
A colleague leaves, and their address is still the recipient of the notification email on a dozen forms. Each form has its own Emails section, so each one is opened by hand.
Cotlet does it in your own 123FormBuilder account with list_forms, list_notification_emails and update_notification_email, called by your AI agent, an n8n workflow or a script.
Hosted · nothing to install or maintain
Can 123FormBuilder do this on its own?
123FormBuilder API v2 has no call for notification emails (checked 23 Oct 2026). The only outbound setting it exposes is a webhook URL on a group, and the API does not list who a form emails. The Zapier app has triggers only.
How you do it in 123FormBuilder today
- Open My Forms and pick the form, then go to Set Up and open Emails.
- A default email is already there, turned on, and goes to the account email address when the form is submitted.
- Under Send to, change the account email, the form's email fields or the typed addresses. Click Add rules to route by an answer.
- Save, then repeat for every other form and every other email on it.
- Nothing in My Forms shows which forms notify which address, so a missed form keeps mailing the old person.
How to change 123FormBuilder notification recipients on many forms
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. - 01
Walk the forms
list_forms returns your forms with their ids. Your agent opens each one with list_notification_emails and keeps those whose Send to holds the old address.
- 02
Show the plan
Before anything changes, the agent lists form, email name and the current and new recipients, so you can drop a form from the batch.
- 03
Change one email at a time
update_notification_email replaces the typed addresses in Send to for that email and leaves the subject and body alone. Emails routed by Add rules conditions are listed for you and not changed.
- 04
Keep other recipients
The agent writes back the full list with the old address swapped, so a second recipient on the same email stays.
- 05
Report what moved
The agent reads the email again after saving and reports forms where the new value did not stick, instead of counting them as done.
What you get back
Forms checked: 14
Changed 11: Send to jan@yourcompany.com -> ops@yourcompany.com
Skipped 2 (recipient set by Add rules): Event signup, Job application
Not emailing Jan: 1 form (Newsletter) Other ways to ask
- Add ops@yourcompany.com as an extra recipient of the default notification on every form and keep the others.
- Change the subject of the notification on Contact us to "New contact request" and leave the recipients.
- List which address each form notifies, change nothing.
What 123FormBuilder allows, and what to know first
- 123FormBuilder sets up a default notification email on every form, turned on and sent to the account email address.
- Send to accepts the account email, an email field of the form or typed addresses; Add rules routes by an answer with Send to or Only send to.
- A form can hold at most 15 email notifications.
- From email can be noreply@123formbuilder.com, noreply@myfor.ms, your own SMTP server or a custom sender domain.
- A custom email template copied to another form does not work properly there, because each field has a unique ID.
update_notification_email asks for your OK by default. To run it on a schedule without you, switch confirmation off for that tool in your dashboard.
Sources: Help: How to set up email notifications · Help: Get around the My Forms section · API v2 Forms reference
Call update_notification_email from a script
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"]}' {
"form_id": 5128403,
"email_id": "default",
"name": "Default notification",
"enabled": true,
"send_to": [
"ops@yourcompany.com"
],
"subject": "New submission: Contact us"
} MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is 123formbuilder_write → update_notification_email. Example data.
Schedule it in n8n, Make, Zapier or cron123FormBuilder tools this automation uses
| Tool | Parameters |
|---|---|
| list_forms | search, cursor |
| list_notification_emails | form_id |
| update_notification_email | form_id, email_id, send_to, subject |
Frequently asked questions
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.
Give your agent access to 123FormBuilder.
Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with 123FormBuilder.