Update Submission
jotform.update_submission
ActionBusiness appsconnection required
Calls the Jotform API with the connection's credentials.
Edit the answers on an existing submission, or clear its unread flag.
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
3 fields, 1 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 |
|---|---|---|---|---|---|
submission_id The submission id, as returned by jotform.list_submissions or the submission trigger. | string | Yes | — | — | 237955080346633702 |
answers The answers to change, keyed by question id — {"3": "Lisa Simpson"}. A question with sub-fields takes <qid>_<sublabel> keys, e.g. {"2_first": "Lisa"}. | object | No | — | ≥ 1 characters | {"3":"Lisa Simpson"} |
mark_read Set true to also clear the submission's unread flag, false to mark it unread again. Leave it unset to leave the flag alone. | boolean | No | — | — | — |
- At least one of answers, mark_read must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"answers": {
"3": "Lisa Simpson"
},
"submission_id": "237955080346633702"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
submission_id The submission that was edited. | string | — |
result Jotform's response content for the edit, verbatim. | object | — |
limit_left API calls the account has left today, as Jotform reports them in 'limit-left'. | number | — |
{
"limit_left": 0,
"result": {},
"submission_id": ""
}See Update 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.