Get Submission
jotform.get_submission
ActionBusiness appsconnection required
Calls the Jotform API with the connection's credentials.
Read one submission, with its answers both raw and flattened by field name.
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
1 field, 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 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"submission_id": "237955080346633702"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
submission The whole submission object as Jotform returned it. | object | — |
answers Jotform's answers map, keyed by question id. | object | — |
fields The same answers flattened to one object keyed by each question's name (else a slug of its label), so a later node can read {{ $json.fields.email }}. | object | — |
limit_left API calls the account has left today, as Jotform reports them in 'limit-left'. | number | — |
{
"answers": {},
"fields": {},
"limit_left": 0,
"submission": {}
}See Get 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.