Jotform automation
Correct Jotform submissions in bulk
A few dozen submissions have a mistyped email domain or a wrong ticket type, and each one has to be opened and edited by hand before the list can be used.
Cotlet does it in your own Jotform account with get_form, list_submissions, get_submission and update_submission, called by your AI agent, an n8n workflow or a script.
Hosted · nothing to install or maintain
Can Jotform do this on its own?
Jotform lets you edit a submission in Tables and Inbox, and its REST API edits a submission with POST /submission/{id} (checked 17 Oct 2026). The official MCP has no tool for editing a submission. Nothing finds every row with the same typo and corrects them in one run, which is the gap this job fills.
How you do it in Jotform today
- In Jotform Tables the user clicks a cell of an entry, types the new value and clicks outside the cell or presses Enter to save it.
- To change an entry the way a respondent would, the user hovers over it, clicks the Three Dots icon, then Edit Entry. That resubmits it.
- In Inbox the user selects the submission, clicks the three dots at the top right and then Edit.
- For a run of similar typos the user filters the table, then repeats the edit on every row.
- The work is slow because every row is a separate edit, and rows with the same typo are easy to miss.
How to correct Jotform submissions in bulk
In my Event registration form, find submissions where the email has a typo like "gmial.com" or "gmail.con", fix the domain, and list what you changed. - 01
Learn the field IDs
get_form returns the form's fields with their IDs, so the agent edits the Email field and not a field that only looks similar.
- 02
Find the bad rows
list_submissions pages through the form and the agent keeps the submissions whose email domain matches your list of typos. A domain that is not on the list is left alone.
- 03
Check before writing
get_submission reads the row again right before the edit. If a colleague already fixed it, the agent logs it as handled.
- 04
Edit in place
update_submission changes only the field you named. It works like the inline edit in Tables, so no notification email or integration runs.
- 05
Report each change
The agent lists the submission ID, the old value and the new value, so the changes can be undone by editing them back.
What you get back
Event registration, 41 submissions checked
Fixed 3:
- 6012345678901234567: jordan.ellis@gmial.com to jordan.ellis@gmail.com
- 6012345678901234588: sam.okafor@gmail.con to sam.okafor@gmail.com
- 6012345678901234601: lee.park@hotmial.com to lee.park@hotmail.com
Left for you 1: an address with no @. Other ways to ask
- Change the ticket type from "Standrad" to "Standard" in every submission of the Event registration form.
- Show me every submission with an empty Phone field and change nothing.
- Trim leading and trailing spaces from the Name field in all submissions from this month.
What Jotform allows, and what to know first
- Inline edit in Jotform Tables does not trigger email notifications, integrations or workflows; Edit Entry resubmits the entry and does.
- Submissions of Sign documents cannot be edited in Inbox.
- A notification email has a setting for "When a Submission Is Edited", which is on by default.
- Deleted submissions go to Trash for 30 days; edits are not versioned, so the agent keeps the old values in its report.
update_submission changes only your own Jotform data and reach no one else, so it runs without asking first.
Sources: Jotform Help: How to Edit Submissions in Jotform Tables · Jotform Help: How to View Form Submissions · Jotform Help: How to Set Up Email Notifications · Jotform API documentation
Call update_submission from a script
curl -X PATCH https://cotlet.dev/api/v1/jotform/submissions/6012345678901234567 \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"answers":{"7":"jordan.ellis@gmail.com"}}' {
"submission_id": "6012345678901234567",
"updated_fields": [
{
"field_id": "7",
"label": "Email",
"old_value": "jordan.ellis@gmial.com",
"new_value": "jordan.ellis@gmail.com"
}
],
"notifications_sent": false
} MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is jotform_write → update_submission. Example data.
Schedule it in n8n, Make, Zapier or cronJotform tools this automation uses
| Tool | Parameters |
|---|---|
| get_form | form_id |
| list_submissions | form_id, created_from, created_to, query, archived, limit, cursor |
| get_submission | submission_id |
| update_submission | submission_id, answers |
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.
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.