The Jotform MCP for teams that automate what happens after the form
Connect Jotform once and your forms, questions, submissions, uploads, folders, and reports become building blocks for visual automations and AI agent workflows. 52 typed nodes over the Jotform API v1, region aware for US, EU, and HIPAA accounts.
What the Jotform MCP connector does
The Jotform connector for Mattering Automations covers the Jotform API v1: list and read forms, read and edit the questions on them, pull submissions with their answers, create and edit submissions, read uploaded files, organize forms into folders, build and read reports, manage workspace labels, register and remove a form's webhook URLs, and check account usage and history. That is 25 read nodes and 27 write nodes, generated from the connector itself so this page cannot drift from what ships.
Each capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and any MCP-capable assistant can use them, and they also power Matter, the platform's built-in AI assistant. Describe the form workflow you want in plain language and it gets built on the canvas in front of you.
The connector is region aware. Every node targets Jotform's standard host by default and a per-node region setting switches it to the EU or HIPAA host, so accounts under data residency or healthcare requirements keep their traffic where it belongs. Jotform Enterprise accounts, which serve the API from their own domain, set an API base override on the node instead.
One connection, three surfaces
- Visual automations. Drag Jotform nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Jotform node, ready to drop on the canvas
52 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 25
Jotform: Get Account History
Get the account activity log: form creations, updates, deletions, and logins.
Jotform: Get Account Settings
Get the account's profile settings (name, email, website, time zone, company, industry).
Jotform: Get Folder
Get one folder with the forms and subfolders it contains.
Jotform: Get Form
Get one form's details: title, status, created/updated timestamps, and submission counts.
Jotform: Get Form Properties
Get every property of a form: layout, styling, redirect/thank-you settings, limits, and notification emails.
Jotform: Get Form Property
Get a single named property of a form (e.g. formWidth or thankurl).
Jotform: Get Form Question
Get the full property set of a single question on a form.
Jotform: Get Form Questions
List a form's questions keyed by question ID (qid), the map you need to read or write submission answers.
Jotform: Get Form Reports
List the reports built from one form, with their type, fields, and public URL.
Jotform: Get Form Submissions
Get the submissions for one form, newest first. Filter, order, and page through the results.
Jotform: Get Form Uploads
List the files uploaded through a form, with name, type, size, and download URL.
Jotform: Get Form Webhooks
List the webhook URLs registered on a form, keyed by their index ('0', '1', ...).
Jotform: Get Label
Get one label's name, colour, owner, and timestamps.
Jotform: Get Label Resources
List the forms, workflows, sheets, and apps tagged with a label.
Jotform: Get Monthly Usage
Get this month's usage counters: submissions, SSL submissions, payments, uploads, views, and API calls.
Jotform: Get Plan Details
Get the published limits and pricing of a Jotform plan. Public endpoint: needs no API key.
Jotform: Get Report
Get one report's details by ID.
Jotform: Get Submission
Get one submission with its full answer set, submitter IP, status, and timestamps.
Jotform: Get User
Get the account tied to the API key: username, name, email, plan, status, and time zone.
Jotform: List All Submissions
List submissions across every form on the account. The `answers` object holds the response data.
Jotform: List Folders
Get the account's folder tree, including the forms and subfolders in each folder.
Jotform: List Forms
List every form on the account, with title, status, and submission counts.
Jotform: List Labels
Get the account's label tree, including nested sublabels.
Jotform: List Reports
List every report on the account (Excel, CSV, grid, table, calendar, RSS, or visual).
Jotform: List Sub-Users
List sub-user accounts and the forms/folders each one can access.
Action nodes 27
Jotform: Add Form Question
Add a new question to a form (control_textbox, control_dropdown, control_email, ...).
Jotform: Add Form Questions (bulk JSON)
Add several questions to a form in one call from a raw JSON body.
Jotform: Add Form Webhook
Register a webhook URL that Jotform POSTs to on every new submission to the form.
Jotform: Add Resources to Label
Tag forms, workflows, sheets, or portals with a label.
Jotform: Clone Form
Clone an existing form into a new one on the same account.
Jotform: Create Folder
Create a folder for organising forms.
Jotform: Create Form
Create a new form from a questions + properties (+ optional emails) definition.
Jotform: Create Forms (bulk JSON)
Create form(s) from a raw JSON definition (the PUT variant of Create Form).
Jotform: Create Label
Create a workspace label (optionally nested under an existing one).
Jotform: Create Report
Create a report from a form's submissions (grid, table, calendar, Excel, CSV, RSS, or visual).
Jotform: Create Submission
Add a submission to a form. Note: Jotform does not fire the form's emails or integrations for API-created submissions.
Jotform: Create Submissions (bulk JSON)
Add several submissions to a form in one call from a raw JSON body.
Jotform: Delete Folder
Delete a folder. The forms inside it are not deleted.
Jotform: Delete Form
Delete a form. Jotform moves it to the trash (status becomes DELETED) rather than purging it.
Jotform: Delete Form Question
Delete a question from a form.
Jotform: Delete Form Webhook
Remove a webhook from a form by its index key.
Jotform: Delete Label
Delete a label. The resources it tagged are not deleted.
Jotform: Delete Report
Delete a report. The underlying submissions are untouched.
Jotform: Delete Submission
Delete a submission and its answer data.
Jotform: Edit Submission
Edit an existing submission's answers, or mark it read/unread or flagged.
Jotform: Remove Resources from Label
Untag forms, workflows, sheets, or portals from a label.
Jotform: Set Form Properties
Add or edit properties on a form (form-encoded). Only the keys you send are changed.
Jotform: Set Form Properties (JSON)
Add or edit form properties from a raw JSON body (the PUT variant of Set Form Properties).
Jotform: Update Account Settings
Update the account's profile settings. Only the fields you supply are changed.
Jotform: Update Folder
Rename or recolour a folder, or move forms into it.
Jotform: Update Form Question
Edit the properties of an existing question on a form.
Jotform: Update Label
Rename or recolour a label.
Connecting Jotform takes one credential
Jotform connects with a single account API key. Create it in Jotform under My Account, in the API section, and choose the permission level you want the key to carry. Mattering sends it as the APIKEY request header on every call, which is the form Jotform documents. The key never goes in the query string, so it cannot leak into an access log or a referrer.
In Jotform, open My Account and go to the API section, then create a new key and pick its permission level. A read only key is enough for reporting workflows; creating, editing, or deleting anything needs a key with write access.
In Mattering Automations, open Connectors, choose Jotform, and attach a secret holding the key. It is a single field: paste the key on its own, with no prefix and no header name in front of it.
Leave each node's region on the default US host, or switch it to eu or hipaa to match the account the key belongs to. Enterprise accounts set the API base override to their own API domain instead.
Drop a Jotform: Get User node on a canvas and run it with an empty config. A successful response returns the account the key belongs to, and every Jotform node is then ready in the palette.
Common uses for the Jotform MCP
Turn submissions into tracked work
Pull new submissions with Get Form Submissions or List All Submissions on a schedule, read the answers, and open an assigned task in Mattering Productivity, send an email, or post a message, so a form entry becomes something a person is actually accountable for.
Let an agent answer questions about your forms
Give an assistant List Forms, Get Form, Get Monthly Usage, and Get Account History and it can report which forms are collecting responses, which have gone quiet, and what changed on the account last week, without anyone opening the Jotform dashboard.
Build and edit forms from a workflow
Create Form, Add Form Question, Update Form Question, and Set Form Properties let an automation stand up a new intake form, add fields to an existing one, or change the thank you redirect across a set of forms. Clone Form copies a proven form as the starting point.
Route uploaded files onward
Get Form Uploads returns each uploaded file with its name, type, size, and download URL, so an HTTP step can fetch the file and a later node can file it in storage, attach it to a task, or hand it to an AI step for review.
Keep a large form library organized
Folders and labels are both covered: create and update folders, move forms into them, and tag forms, workflows, sheets, and portals with labels, so an account with hundreds of forms stays navigable as it grows.
Audit and maintain form webhooks
Get Form Webhooks lists what each form posts to, and Add Form Webhook and Delete Form Webhook change those registrations. Run it across your forms to find stale endpoints or roll a webhook URL everywhere in one pass instead of clicking through each form's settings.
Example: Morning sweep turns overnight submissions into assigned tasks
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a schedule in Mattering Automations runs each morning.
Jotform: Get Form Questions reads the question map for your intake form, so answers can be labeled rather than shown as bare question ids.
Jotform: Get Form Submissions pulls the submissions created since the last run, newest first.
An AI step reads each submission and writes a short summary with a suggested owner and priority.
Mattering Productivity: a task is created per submission with the summary, the answers, and a link back to the form, assigned to the owner the AI step picked.
Jotform MCP questions, answered
Can a new Jotform submission trigger a Mattering workflow?
Not yet, and it is worth being clear about it. The three webhook nodes manage a form's webhook registrations: they list the URLs a form posts to, add one, and remove one. They do not give Mattering an inbound endpoint that a Jotform submission can start a workflow from. To act on new submissions today, run Get Form Submissions on a schedule and process what is new since the last run. A native Jotform trigger is a candidate for a later connector update.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and work with Jotform through them. Matter, the assistant built into the platform, uses the same nodes natively.
Can an AI agent read submissions and act on them?
Yes. An agent can list submissions across the account or for one form, read a single submission with its full answer set, edit an existing submission, mark it read or flagged, and delete one. Because answers come back keyed by question id, agents usually read Get Form Questions first so they can talk about fields by name.
What credential does the connector use?
One Jotform account API key, stored encrypted in Google Secret Manager and sent as the APIKEY request header. It is a single value credential, so paste the key by itself. This is the most common setup mistake to avoid: Jotform does not use an Authorization bearer token, and adding a prefix or the header name to the value will produce a 401 on every node.
Does it work with EU, HIPAA, or Enterprise Jotform accounts?
Yes. Every node carries a region setting, with the standard US host as the default and eu and hipaa options that point at Jotform's EU and HIPAA hosts. Enterprise accounts, whose API lives on a per customer domain, set the API base override on the node instead. This matters beyond convenience: a HIPAA account's data has to stay on the HIPAA host, and the setting is what keeps it there.
Can it create forms and submissions, or only read them?
Both. 27 of the 52 nodes write: create and clone forms, add, update, and delete questions, set form properties, create and edit submissions, create folders, reports, and labels, and delete each of those. One caveat worth knowing before you backfill data: Jotform documents that a submission created through the API does not fire the form's notification emails or its integrations.
What about labels and the parts of the API that are not covered?
The eight label nodes match Jotform's documented label endpoints, but labels read as a workspace surface and their availability on lower plans is not something we can confirm, so treat them as plan dependent. Two documented paths, the account invoices call and the single settings key lookup, were left out because Jotform publishes no parameter or response contract for either, and guessing at a contract is worse than leaving the node off.
What are Jotform's API limits?
Jotform documents a daily API request allowance that varies by plan, and every response carries a limit left value showing what remains for the day. Node outputs surface that value, so a workflow doing a bulk pull can read it in a condition node and stop or slow down before it runs the account out.
Put Jotform to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Jotform is a product of its respective owner; Mattering is an independent platform.