Create Submissions (bulk)

jotform.create_submissions
ActionBusiness appsconnection required

Calls the Jotform API with the connection's credentials.

File several submissions against one form in a single call.

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.

FieldTypeRequiredDefaultConstraintsExample
form_id
The form to file the submissions against.
stringYes——240123456789012
submissions
A JSON array of submissions, each an object of question id to value: [{"1": {"text": "answer of Question 1"}}]. Jotform takes this call as a raw JSON body rather than a form post.
arrayYes—≥ 1 characters; array of object[{"1":{"text":"answer of Question 1"}}]

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "form_id": "240123456789012",
  "submissions": [
    {
      "1": {
        "text": "answer of Question 1"
      }
    }
  ]
}

Output

One shape.

result

FieldTypeExample
result
Jotform's response for the batch, exactly as returned — one {submissionID, URL} entry per row it accepted. Jotform documents no per-row status here, so nothing is flattened into an ok/fail verdict.
array—
submitted
How many rows were sent, when the array was countable.
number—
limit_left
API calls the account has left today, as Jotform reports them in 'limit-left'.
number—
{
  "limit_left": 0,
  "result": [],
  "submitted": 0
}

Notes

  • Jotform reports no per-row outcome for the bulk call — check 'result' before treating every row as filed.

See Create Submissions (bulk) 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.