Reference · Tools

JotForm Trigger

Starts workflow when a JotForm form is submitted

Webhook trigger Utility v1

The JotForm Trigger fires when a form you nominate is submitted, delivering the submission to the workflow. Resolve Data converts JotForm's internal field keys into readable question names, and Only Answers strips the metadata. A typical build is routing each submission into a CRM with fields that are actually readable.

Node type
Webhook trigger
Parameters
3
Outputs
Output
Credentials
JotForm API

JotForm Trigger

Trigger on JotForm form submissions

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.

Category: Utility
Tool Name: jotform_trigger
Version: 1

Appearance: Icon: lucide-ClipboardList | Color: #09f

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

DirectionPort(s)
InputNone (trigger node)
OutputOutput

Credentials

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

Parameters

ParameterTypeRequiredDefaultDescription
FormstringYesThe JotForm form ID to listen for submissions on. You can find this in your JotForm form URL.
Resolve DatabooleanNotrueWhen 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 AnswersbooleanNotrueWhen 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.

Usage Examples

  • Trigger when a JotForm form is submitted
  • Receive JotForm submission data with resolved field names
  • Start workflow on new form response from JotForm

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

Receives JotForm form submissions via webhook. Configure the Form ID to listen on. Enable Resolve Data to convert internal field keys to readable question names. Enable Only Answers to receive just the form answers without metadata.

Frequently asked questions

Why are my fields named things like q3_email?

Those are JotForm's internal field keys. Turn on Resolve Data and the trigger converts them into the readable question names from the form.

How do I get just the answers?

Turn on Only Answers to receive the form answers without the surrounding submission metadata — cleaner when you are mapping straight into another system.

Which form does it listen to?

The one whose Form ID you configure. Use a separate trigger per form you want to watch.

Which credential does it need?

A JotForm API credential, used to register the webhook against the form.

Build with the JotForm Trigger node

Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need JotForm API credentials first.

Open BusyBot

Last updated . Spotted something wrong? Tell us.