Get JotForm Submission: JotForm action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Submission ID submissionId	string	Required	The unique submission ID returned by Jotform after a form is submitted (a 19-digit number). Find via List Submissions. This is NOT the form ID.

Sample request

{
  "submissionId": "e.g. 6490309715515612677"
}

Returns

{
  "content": {
    "id": "sub123",
    "status": "ACTIVE",
    "answers": {
      "1": {
        "text": "Name",
        "answer": "John Doe"
      }
    },
    "form_id": "form123",
    "created_at": "2026-04-11 10:00:00"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get JotForm Submission.

What does the Get JotForm Submission action do in JotForm?

Returns one submission by ID with all answers. Useful for re-fetching submissions captured upstream.

What inputs does Get JotForm Submission require?

Required: Submission ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if JotForm returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get JotForm Submission support batch operations?

Yes. Run Get JotForm Submission inside a Loop node to process arrays. Tiny Command handles JotForm's rate limits automatically so you don't have to throttle manually.

More actions