JotForm trigger

Overview

Webhook trigger that listens for JotForm form submissions. When a form is submitted, JotForm sends the submission data via webhook POST. The trigger can optionally resolve internal field keys (e.g., q3_firstName) to human-readable question text (e.g., First Name) by querying the JotForm questions API. Supports filtering to return only answer data or full submission metadata including submission ID, IP, timestamps, and form ID.

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires JotForm API credentials. See the Credentials Guide for setup instructions.

Parameters

Parameter	Type	Required	Default	Description
Form	string	Yes	—	The JotForm form ID to listen for submissions on. You can find this in your JotForm form URL.
Resolve Data	boolean	No	true	When enabled, internal field keys (like q3_firstName) are replaced with the human-readable question text (like First Name) by querying the form question definitions.
Only Answers	boolean	No	true	When enabled, only form answer data is returned. When disabled, full submission metadata (ID, IP, timestamps, etc.) is included alongside the answers.

Output Data

Each submission produces one output item. What lands on it depends on Only Answers.

With Only Answers enabled (the default), the item carries the parsed form answers plus five metadata fields:

{
  "q3_firstName": "Jane",
  "q4_email": "jane@example.com",
  "_trigger": "jotform_webhook",
  "_timestamp": "2026-01-01T00:00:00.000Z",
  "_webhookEvent": "form.submission",
  "_formId": "",
  "_submissionId": ""
}

With Only Answers disabled, the item carries the submission metadata JotForm posted and the parsed answers nested under rawRequest:

{
  "submissionID": "",
  "formID": "",
  "ip": "",
  "createdAt": "",
  "rawRequest": {},
  "_trigger": "jotform_webhook",
  "_timestamp": "2026-01-01T00:00:00.000Z",
  "_webhookEvent": "form.submission",
  "_formId": "",
  "_submissionId": ""
}

• _trigger — always jotform_webhook.
• _timestamp — ISO 8601 timestamp of when the submission arrived.
• _webhookEvent — always form.submission.
• _formId — the submitting form’s ID, taken from the payload.
• _submissionId — the submission’s ID, taken from the payload.

JotForm posts the answers as a JSON string in rawRequest; the trigger parses it for you. If that string is not valid JSON, the parsed object instead contains _rawParseError: true and the original text under rawValue.

Reference answers downstream by expression, for example {{ $json.q4_email }} when Only Answers is on, or {{ $json.rawRequest.q4_email }} when it is off.

Example Configuration

Receive just the answers from a form:

{
  "type": "jotform_trigger",
  "parameters": {
    "form": "240123456789012",
    "resolveData": true,
    "onlyAnswers": true
  }
}

Receive the full submission, metadata included:

{
  "type": "jotform_trigger",
  "parameters": {
    "form": "240123456789012",
    "resolveData": true,
    "onlyAnswers": false
  }
}

Keep the raw JotForm field keys instead of question labels:

{
  "type": "jotform_trigger",
  "parameters": {
    "form": "240123456789012",
    "resolveData": false,
    "onlyAnswers": true
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

This tool receives JotForm form submissions. It is ideal when you need to start a workflow based on new responses to a specific JotForm form, optionally resolving internal field keys to human-readable question names. It produces either the raw form answers or full submission metadata, including submission ID, IP, timestamps, and form ID.