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

# Change Jotform notification recipients on many forms

> Move Jotform notification emails from one person to another across all your forms in one run, with a list of every form changed.

Source: https://cotlet.dev/integrations/jotform-api-mcp-server/change-form-notification-recipients

A colleague leaves or changes role, and their address sits in the notification email of dozens of forms. Each form has to be opened in Form Builder, one by one.

Cotlet does it in your own Jotform account with list\_forms, list\_notification\_emails and set\_notification\_recipients, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=jotform) [All Jotform tools](https://cotlet.dev/integrations/jotform-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Jotform do this on its own?

Jotform sets notification recipients per form in Form Builder, and its REST API changes form properties (checked 17 Oct 2026). A dedicated endpoint for notification emails is not documented in what we read, and the official MCP has no tool for it. Nothing finds every form that notifies one person and changes them together, which is the gap this job fills.

## How you do it in Jotform today

1. In Form Builder the user clicks Settings in the orange top bar and then Emails in the left menu.
2. The user opens the Notification Email in the list of emails.
3. On the Email tab the user edits the Recipients field and the CC and BCC fields.
4. The user clicks Save Email.
5. The user repeats this for every form, and a form with two notification emails needs it twice.

## How to change Jotform notification recipients on many forms

Prompt

```
Our support lead changed. On every form whose notification email goes to maria@example.com, send it to dana@example.com instead, keep the CC, and list the forms you changed.
```

1. 01  
### List the forms  
list\_forms returns your forms with their IDs, and the agent walks through all of them, not only the first page.
2. 02  
### Read each notification email  
list\_notification\_emails shows who receives each email on a form. The agent keeps only the emails that name the person you are replacing.
3. 03  
### Check the plan limit  
A free account has one Notification Email and one recipient per form. If the new list is longer than the plan allows, the agent reports the form instead of cutting recipients.
4. 04  
### Replace the address  
set\_notification\_recipients swaps the address and leaves CC, BCC, subject and body as they were. It asks for your OK on every form until you switch confirmation off.
5. 05  
### Report the result  
The agent lists the forms it changed, the old and new recipients, and the forms it skipped with the reason.

### What you get back

Example data

```
Forms checked: 18
Changed 6: Event registration, Newsletter signup, Contact us, Job application, Refund request, Feedback
Skipped 1: Partner intake (maria@example.com is a CC, not a recipient)
Not affected: 11 forms.
```

### Other ways to ask

- Add dana@example.com as a CC on every Notification Email of the Contact us form and change nothing else.
- List every form whose notification goes to an address outside example.com and change nothing.
- Remove maria@example.com from CC and BCC on all forms.

## What Jotform allows, and what to know first

- A Notification Email is created automatically once a form has at least one field.
- The Starter (free) plan allows one Notification Email and one recipient per form; paid plans allow up to 10 recipients in total on a Notification Email.
- "Send Email Automatically" has two events, "When a Submission Is Received" and "When a Submission Is Edited", both on by default.
- The Sender Name, Sender Email and Reply-To Email are set on the Advanced tab; a custom sender goes through Manage Sender Emails.

set\_notification\_recipients asks for your OK by default. To run it on a schedule without you, switch confirmation off for that tool in your dashboard.

Sources: [Jotform Help: How to Set Up Email Notifications](https://www.jotform.com/help/25-setting-up-email-notifications/) · [Jotform API documentation](https://api.jotform.com/docs/) · [Jotform MCP server](https://www.jotform.com/mcp/)

## Call set\_notification\_recipients from a script

curl

```
curl -X PUT https://cotlet.dev/api/v1/jotform/forms/242831904782058/notification-recipients \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email_id":"1","recipients":["dana@example.com"],"cc":["team@example.com"]}'
```

Example response

```
{
"form_id": "242831904782058",
"email_id": "1",
"recipients": [
"dana@example.com"
],
"cc": [
"team@example.com"
],
"bcc": []
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is jotform\_write → set\_notification\_recipients. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/jotform-api-mcp-server.md#automations)

## Jotform tools this automation uses

__Cotlet Jotform tools used to change Jotform notification recipients on many forms__
| Tool | Parameters |
| ----------------------------- | ---------------------------------------- |
| list\_forms | query, limit, cursor |
| list\_notification\_emails | form\_id |
| set\_notification\_recipients | form\_id, email\_id, recipients, cc, bcc |

[All 10 Jotform tools with descriptions](https://cotlet.dev/integrations/jotform-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Jotform to Cotlet?

Yes. You sign in to Jotform yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Jotform 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.

## More Jotform automations

- [Build Jotform response reports with AI](https://cotlet.dev/integrations/jotform-api-mcp-server/build-form-response-reports.md)
- [Correct Jotform submissions in bulk](https://cotlet.dev/integrations/jotform-api-mcp-server/correct-submission-data.md)
- [Jotform API and MCP server: every tool](https://cotlet.dev/integrations/jotform-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Jotform.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Jotform.

[Sign up free](https://cotlet.dev/app/signup?app=jotform)

---

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.