Create Submission
jotform.create_submission
ActionBusiness appsconnection required
Calls the Jotform API with the connection's credentials.
File one submission against a form, as if somebody had filled it in.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Jotform
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- region, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
form_id The form to file the submission against. | string | Yes | — | — | 240123456789012 |
answers The answers to file, keyed by question id — {"3": "Bart Simpson"}. A question with sub-fields takes <qid>_<sublabel> keys, e.g. {"2_first": "Bart"}, exactly as Jotform's own reference posts them. | object | Yes | — | ≥ 1 characters | {"3":"Bart Simpson"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"answers": {
"3": "Bart Simpson"
},
"form_id": "240123456789012"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
submission_id The id Jotform gave the new submission. | string | — |
url The API URL of the new submission. | string | — |
created Jotform's create response, verbatim. | object | — |
limit_left API calls the account has left today, as Jotform reports them in 'limit-left'. | number | — |
{
"created": {},
"limit_left": 0,
"submission_id": "",
"url": ""
}See Create Submission run in a workflow.
In a technical demo we add the Jotform connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.