> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.meetgail.com/platform/workflows/node-reference/integrations/jotform/jot-form-submit/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.meetgail.com/_mcp/server.

# JotForm Submit

> Submits answers to a JotForm form, labeling each answer with the form's question label.

The Submit node sends a set of answers to one of your JotForm forms, creating a
new submission. You label each answer with the question's label as it reads on the
form, and the node lines your answers up with the right questions.

## When to use it

* You want to record data your workflow gathered as a JotForm submission.
* You collect leads or intake details and want them to land in an existing form.
* You want to feed answers from an earlier step straight into a form.

## Inputs

| Field   | What it's for                                             | Example                                                         |
| ------- | --------------------------------------------------------- | --------------------------------------------------------------- |
| Form    | The JotForm form to submit to, identified by its form id. | `260056698857069`                                               |
| Answers | Each answer labeled with the form's question label.       | `First Name: Sarah`, `Email: sarah@...`                         |
| API key | Your JotForm API key, stored as a secret.                 | A [Secret](/platform/workflows/core-concepts/secrets) reference |

The form and answers can be fixed values or [expressions](/platform/workflows/core-concepts/expressions/using-expressions-in-nodes)
that read from an earlier step. The API key must reference a workflow
[Secret](/platform/workflows/core-concepts/secrets). For a multi-part field like Full Name,
label each part with its own label ("First Name", "Last Name").

## Outputs

| Field         | What you get back                              |
| ------------- | ---------------------------------------------- |
| Submission id | The id of the new submission that was created. |

## Example

Chen Insurance Group runs a JotForm intake form for new prospects. When a lead
arrives through another channel, a workflow uses Submit to record it: it labels
the answers "First Name" as `Sarah`, "Last Name" as `Chen`, and "Email" as her
address, with the API key supplied from a secret. JotForm hands back the new
submission id for the run to log.

![The JotForm Submit node configuration panel, showing the form id, answers, and API key.](/_fern-img/bb3529d0f67149e9d6d6138e3d7be816adec0ba4ba84a64707242bdf53f43920.webp)

> **Note**
>
> Answer labels must match the question labels on the form, matched without regard
> to case. If a label matches no question, the node reports the unmatched labels
> instead of submitting - copy the labels exactly as they read on the form.

## Related nodes

#### [Data Transform](/platform/workflows/node-reference/logic-and-flow/data-transform)

Shape earlier data into the answers you submit.

#### [Check](/platform/workflows/node-reference/logic-and-flow/check)

Branch on whether the submission succeeded.

> Documentation for Gail, the AI platform for financial services. Learn how to set up GailGPT and Gail Agent to automate customer communications for insurance, banking, and finance.