Mattering Automations Jotform integration

Connect Jotform to Mattering Automations: forms, questions, submissions, uploads, folders, reports, labels, and form webhook registrations as workflow steps, authenticated with a Jotform account API key.

Get the credential Connect Verify Node reference Troubleshooting

The Mattering Automations Jotform integration adds Jotform to your automation canvas: list and read forms, read and edit their questions, pull and write submissions, list uploaded files, organize forms into folders, build reports, manage workspace labels, and register or remove the webhook URLs a form posts to.

Setup takes a few minutes: create an API key in your Jotform account, attach it as a credential in Mattering, set the region if your account is not on the standard host, and run one read only node to confirm it works. This guide walks through each step and ends with the full node reference.

Before you start

A Jotform account with access to the forms you want to automate.
Permission to create an API key on that account, from the API screen under My Account.
A Mattering workspace with access to the Automations app.
Knowledge of which Jotform host your account uses: the standard host, the EU host, the HIPAA host, or an Enterprise domain of your own.

Create a Jotform API key

Mattering authenticates to Jotform with a single account API key, sent as the APIKEY request header on every call. Jotform also accepts the key as a query string parameter; Mattering never uses that form, so the key cannot end up in an access log, a proxy log, or a referrer header.

In Jotform, open My Account and go to the API section (jotform.com/myaccount/api).

Click Create New Key and choose the permission level the key should carry. A read only key covers reporting and monitoring workflows; anything that creates, edits, or deletes needs a key with write access.

If your security policy calls for it, add an IP restriction to the key on the same screen.

Copy the key.

Store the key value on its own. Jotform does not use an Authorization bearer token, so do not add a Bearer prefix, and do not type the header name APIKEY into the value field. Either mistake produces a 401 on every node with a key that is otherwise valid.

Connect Jotform to Mattering

In Mattering Automations, open Connectors and click Add Connector.

Choose Jotform from the list.

Click Create new credential, paste your API key into the single value field, and save.

The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.

Click Connect. All 52 Jotform nodes appear in your canvas palette.

Every node has a region setting that defaults to us (api.jotform.com). Set it to eu (eu-api.jotform.com) or hipaa (hipaa-api.jotform.com) if that is where the account behind the key lives. Jotform Enterprise accounts serve the API from their own domain, so those set the api base field on the node instead; it overrides the region.

Verify it works

This connector has no Test Connection button. Its credential is a plain single value secret, and the generic connection test would send the value without the APIKEY header, so it would tell you nothing useful. Verify by running a node instead.

Open any automation canvas and check the palette: a Jotform section should list the query and action nodes. Drop Jotform: Get User onto the canvas, leave the config empty, set the region to match your account, and run a test step. It takes no parameters and is a safe, read only call, so a successful response returns the account behind the key: username, name, email, plan, and time zone.

To confirm form access, add Jotform: List Forms and run it. A successful response lists your forms with their ids, titles, statuses, and submission counts. Note the numeric form id of the form you want to automate; almost every other node asks for it.

Every Jotform response also carries a limit left value: the API calls remaining on the account's daily allowance. It is worth reading in a condition node before a bulk pull.

Node reference

52 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 25

Jotform: Get Account History

jotform_get_history

Get the account activity log: form creations, updates, deletions, and logins.

Jotform: Get Account Settings

jotform_get_settings

Get the account's profile settings (name, email, website, time zone, company, industry).

Jotform: Get Folder

jotform_get_folder

Get one folder with the forms and subfolders it contains.

Jotform: Get Form

jotform_get_form

Get one form's details: title, status, created/updated timestamps, and submission counts.

Jotform: Get Form Properties

jotform_get_form_properties

Get every property of a form: layout, styling, redirect/thank-you settings, limits, and notification emails.

Jotform: Get Form Property

jotform_get_form_property

Get a single named property of a form (e.g. formWidth or thankurl).

Jotform: Get Form Question

jotform_get_form_question

Get the full property set of a single question on a form.

Jotform: Get Form Questions

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

jotform_get_form_reports

List the reports built from one form, with their type, fields, and public URL.

Jotform: Get Form Submissions

jotform_get_form_submissions

Get the submissions for one form, newest first. Filter, order, and page through the results.

Jotform: Get Form Uploads

jotform_get_form_files

List the files uploaded through a form, with name, type, size, and download URL.

Jotform: Get Form Webhooks

jotform_get_form_webhooks

List the webhook URLs registered on a form, keyed by their index ('0', '1', ...).

Jotform: Get Label

jotform_get_label

Get one label's name, colour, owner, and timestamps.

Jotform: Get Label Resources

jotform_get_label_resources

List the forms, workflows, sheets, and apps tagged with a label.

Jotform: Get Monthly Usage

jotform_get_usage

Get this month's usage counters: submissions, SSL submissions, payments, uploads, views, and API calls.

Jotform: Get Plan Details

jotform_get_plan

Get the published limits and pricing of a Jotform plan. Public endpoint: needs no API key.

Jotform: Get Report

jotform_get_report

Get one report's details by ID.

Jotform: Get Submission

jotform_get_submission

Get one submission with its full answer set, submitter IP, status, and timestamps.

Jotform: Get User

jotform_get_user

Get the account tied to the API key: username, name, email, plan, status, and time zone.

Jotform: List All Submissions

jotform_list_submissions

List submissions across every form on the account. The `answers` object holds the response data.

Jotform: List Folders

jotform_list_folders

Get the account's folder tree, including the forms and subfolders in each folder.

Jotform: List Forms

jotform_list_forms

List every form on the account, with title, status, and submission counts.

Jotform: List Labels

jotform_list_labels

Get the account's label tree, including nested sublabels.

Jotform: List Reports

jotform_list_reports

List every report on the account (Excel, CSV, grid, table, calendar, RSS, or visual).

Jotform: List Sub-Users

jotform_list_subusers

List sub-user accounts and the forms/folders each one can access.

Action nodes 27

Jotform: Add Form Question

jotform_create_form_question

Add a new question to a form (control_textbox, control_dropdown, control_email, ...).

Jotform: Add Form Questions (bulk JSON)

jotform_create_form_questions_bulk

Add several questions to a form in one call from a raw JSON body.

Jotform: Add Form Webhook

jotform_create_form_webhook

Jotform: Add Resources to Label

jotform_add_label_resources

Tag forms, workflows, sheets, or portals with a label.

Jotform: Clone Form

jotform_clone_form

Clone an existing form into a new one on the same account.

Jotform: Create Folder

jotform_create_folder

Create a folder for organising forms.

Jotform: Create Form

jotform_create_form

Create a new form from a questions + properties (+ optional emails) definition.

Jotform: Create Forms (bulk JSON)

jotform_create_forms_bulk

Create form(s) from a raw JSON definition (the PUT variant of Create Form).

Jotform: Create Label

jotform_create_label

Create a workspace label (optionally nested under an existing one).

Jotform: Create Report

jotform_create_report

Create a report from a form's submissions (grid, table, calendar, Excel, CSV, RSS, or visual).

Jotform: Create Submission

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)

jotform_create_submissions_bulk

Add several submissions to a form in one call from a raw JSON body.

Jotform: Delete Folder

jotform_delete_folder

Delete a folder. The forms inside it are not deleted.

Jotform: Delete Form

jotform_delete_form

Delete a form. Jotform moves it to the trash (status becomes DELETED) rather than purging it.

Jotform: Delete Form Question

jotform_delete_form_question

Delete a question from a form.

Jotform: Delete Form Webhook

jotform_delete_form_webhook

Remove a webhook from a form by its index key.

Jotform: Delete Label

jotform_delete_label

Delete a label. The resources it tagged are not deleted.

Jotform: Delete Report

jotform_delete_report

Delete a report. The underlying submissions are untouched.

Jotform: Delete Submission

jotform_delete_submission

Delete a submission and its answer data.

Jotform: Edit Submission

jotform_edit_submission

Edit an existing submission's answers, or mark it read/unread or flagged.

Jotform: Remove Resources from Label

jotform_remove_label_resources

Untag forms, workflows, sheets, or portals from a label.

Jotform: Set Form Properties

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)

jotform_replace_form_properties

Add or edit form properties from a raw JSON body (the PUT variant of Set Form Properties).

Jotform: Update Account Settings

jotform_update_settings

Update the account's profile settings. Only the fields you supply are changed.

Jotform: Update Folder

jotform_update_folder

Rename or recolour a folder, or move forms into it.

Jotform: Update Form Question

jotform_update_form_question

Edit the properties of an existing question on a form.

Jotform: Update Label

jotform_update_label

Rename or recolour a label.

Using the integration

On the automation canvas

Jotform nodes chain with every other node: a submission can become an assigned task in Mattering Productivity, an AI step can summarize a long answer before anyone reads it, and an uploaded file's download URL can be handed to an HTTP node in the same flow.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can list forms, read submissions, add questions, and file forms into folders through the same nodes your workflows use.

Answers are keyed by question id

Jotform returns and accepts submission answers keyed by question id (qid), not by the field label a person sees. Run the Get Form Questions node first and keep that map: it is what lets you read an answer by name, and it is required to write one with Create Submission or Edit Submission.

Region and Enterprise hosts

Jotform serves the same API from a standard host, an EU host, a HIPAA host, and per customer Enterprise domains. The region setting picks the first three and the api base field covers the fourth. Set it deliberately: routing data from a HIPAA account through the standard host is a compliance problem, and this field is what prevents it.

Reacting to new submissions

The webhook nodes manage a form's webhook registrations, they are not an inbound trigger, so a Jotform submission cannot start a Mattering workflow on its own yet. Poll instead: run the Get Form Submissions node on a schedule, filtered or ordered by creation time, and process what is new since the last run.

Managing webhooks across many forms

Where the webhook nodes do earn their place is maintenance. Get Form Webhooks reports what each form posts to, and Add Form Webhook and Delete Form Webhook change those registrations, so you can audit or roll an endpoint across a whole form library in one run.

Troubleshooting

Every node returns a 401 Unauthorized

Three usual causes. The stored value is not just the key: a Bearer prefix or the word APIKEY typed into the value field both break it. The key was created read only and the node is trying to write, which Jotform rejects rather than partially applying. Or the key carries an IP restriction that does not include the address Mattering calls from. Regenerate or re-scope the key in the Jotform API screen and update the credential on the connector.

A valid key returns 401 or empty results on an EU or HIPAA account

The node is calling the wrong host. A key issued on an EU or HIPAA Jotform account does not authenticate against the standard host, and where it does answer it will not find your forms. Set the node's region to eu or hipaa. Jotform Enterprise accounts set the api base field to their own API domain, which overrides the region.

A node returns 404 for a form you can see in Jotform

The form id field wants Jotform's numeric form id, not the form's title. Run Jotform: List Forms and copy the id, or read it from the form's URL. The same applies to submission, report, folder, and label ids: read them from the matching list node rather than typing a name.

A submission write succeeds but the answers are empty

Answers are keyed by question id, not by field label, so a body built from labels posts nothing Jotform recognizes and the call can still return success. Run Jotform: Get Form Questions first, map each field to its qid, and build the submission object from those keys.

An API created submission does not send the form's notification email

That is Jotform's documented behavior, not a connector fault: form emails and integrations do not fire for submissions created through the API. If a backfill or an automation needs to notify someone, send that notification as its own step in the workflow.

The label nodes fail on a non Enterprise plan

The eight label nodes match Jotform's documented label endpoints, but labels read as a workspace surface and availability on lower plans is not something we can confirm. If they error on your account, treat labels as plan dependent and use folders, which are available more broadly, to organize forms instead.

Delete Form Webhook does not remove the webhook

The webhook id is the index key Jotform returns from Jotform: Get Form Webhooks, the string '0' or '1', not the webhook URL and not a UUID. Read the current list first and pass the key from it.

A deleted form still appears in List Forms

Delete Form is a soft delete: Jotform moves the form to the trash and its status becomes DELETED rather than purging it. Filter on status if a workflow should ignore trashed forms, and empty the trash in Jotform when you want the form gone for good.

The Jotform MCP

What connecting Jotform unlocks for AI agents and automations, with common uses and FAQs.

More guides

All Automations documentation

Every integration guide, plus how connectors, credentials, and workflows fit together.

Jotform is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.