What format does Jotform use to send webhook data?

Jotform sends webhooks as an HTTP POST with form-encoded body. Each field appears as a separate key using the pattern q{N}_{fieldName}, where N is the field's order number in the form builder. The payload also includes a rawRequest key containing all the same data as a JSON string, which is easier to parse. Top-level keys include submissionID, formID, formTitle, and each q{N} field.

How do I find my form's exact field key names?

Use Jotform's built-in Test Webhook button. Go to Settings then Integrations, find your webhook, and click Test. Jotform sends a sample payload to your endpoint. In WA.Expert, open the automation's test mode and inspect the received payload to see the exact q{N}_fieldname keys and their values for your specific form.

Why does the Name field return an object instead of a string?

Jotform's Full Name field type splits the name into first and last subfields. In the rawRequest JSON, the name field appears as an object: {first: 'Priya', last: 'Sharma'}. To get the first name, map rawRequest.q4_name.first. To get the last name, map rawRequest.q4_name.last. If you used a Short Text field for the name instead of the Full Name field, it returns a plain string.

Can I change the q{N} prefix on my field keys?

No. The q{N} prefix is auto-assigned based on the order the field was added to the form and cannot be changed. The number is a unique field identifier, not the field's position in the current layout. When you delete and re-add a field, it gets a new number. The safest approach is to use the Test Webhook to discover the exact key names for your form.

Connect Jotform to WhatsApp — Form Alert Guide

Jotform webhooks work on all plans including Free

Unlike Calendly (Standard plan required) or Typeform (paid plans), Jotform webhooks are available on the Free plan. Free plan: up to 5 forms, 100 submissions per month.

Jotform uses q{N}_fieldname keys: always use Test Webhook first

Jotform field keys follow the pattern q4_name, q5_email, where the number is the order the field was added to the form. This number cannot be changed and is unique to your form. Always click Test on the webhook to see your exact keys before mapping them in WA.Expert.

Step 1: Get your WA.Expert webhook URL

In WA.Expert, create a new automation and set the trigger to Inbound Webhook. Copy the unique webhook URL from the trigger settings.

Step 2: Add the webhook in Jotform

Open your Jotform. Click Settings in the top bar.

Click Integrations in the left sidebar. Search for Webhooks and click it.

Paste your WA.Expert webhook URL in the Webhook URL field and click Complete Integration.

Click Test on the webhook entry. This sends a real sample payload to WA.Expert. Check your automation's test mode to see the exact field keys.

Official docs

Jotform Webhooks: jotform.com/help

Step 3: Understand the payload structure

Jotform sends the webhook as a form-encoded POST. The body contains individual field keys and a rawRequest key with all fields as a JSON string. Use rawRequest for the cleanest mapping in WA.Expert.

Jotform webhook payload — top-level fields

POST to your WA.Expert webhook URL
Content-Type: application/x-www-form-urlencoded

Top-level keys:
  submissionID  = '5748291039845829361'
  formID        = '71406408'
  formTitle     = 'Contact Us'
  q4_name       = '{{"first":"Priya","last":"Sharma"}}'
  q5_email      = 'priya@example.com'
  q6_phoneNumber= '+919820000001'
  q7_message    = 'I am interested in a product demo'
  rawRequest    = '{...JSON string of all fields...}'

rawRequest parsed:
{{
  "q4_name":        {{"first": "Priya", "last": "Sharma"}},
  "q5_email":       "priya@example.com",
  "q6_phoneNumber": "+919820000001",
  "q7_message":     "I am interested in a product demo"
}}

Map these paths to WA.Expert variables:

Variable	Path in rawRequest	Example value
customer_name	q4_name.first + ' ' + q4_name.last	Priya Sharma
customer_first	q4_name.first	Priya
customer_email	q5_email	priya@example.com
customer_phone	q6_phoneNumber	+919820000001
customer_message	q7_message	I am interested in a product demo
submission_id	submissionID	5748291039845829361

Your field numbers (q4, q5, q6, q7) will differ. Use the Test Webhook button to see your exact keys. The number after 'q' is fixed and cannot be changed.

Name field returns an object, not a string

Jotform's built-in Full Name field splits the name into subfields. In rawRequest, it appears as: q4_name: {{first: 'Priya', last: 'Sharma'}}. To get the full name, combine rawRequest.q4_name.first and rawRequest.q4_name.last. If you used a Short Text field for the name instead, it returns a plain string.

Step 4: Discover your exact field keys

Because Jotform field keys are unique to each form, the fastest way to find them is with the built-in test.

In Jotform Settings → Integrations → Webhooks, click Test next to your webhook.

In WA.Expert, open the automation and view the received test payload.

Note the rawRequest value. Parse it as JSON to see all your qN_fieldname keys.


      4

        Map each key to a WA.Expert variable using the paths you discovered.



    
    
      Worked example: contact form to WhatsApp alert
    Full flow — Jotform submission to WhatsApp
1. Priya submits your Jotform contact form:
   Name: Priya Sharma | Phone: +919820000001
   Email: priya@example.com | Message: Product demo

2. Jotform POSTs to your WA.Expert webhook URL.

3. WA.Expert parses rawRequest JSON and maps:
   customer_name  = rawRequest.q4_name.first + ' ' + rawRequest.q4_name.last
   customer_phone = rawRequest.q6_phoneNumber
   customer_email = rawRequest.q5_email
   customer_message = rawRequest.q7_message

4. WA.Expert sends your team:
   'New Jotform lead: Priya Sharma (+919820000001)
    Product demo | priya@example.com'

5. WA.Expert sends Priya:
   'Hi Priya, thanks for reaching out!
    We have received your enquiry and will contact you
    on this number within 2 hours.'

    
    Troubleshooting
    Symptom Likely cause Fix
No webhook firing Wrong URL or integration not saved In Jotform Settings → Integrations → Webhooks, confirm the URL and status. Click Test to send a sample payload and verify receipt.
Empty name or garbled value Mapping q4_name as string The Full Name field is an object: {first, last}. Map rawRequest.q4_name.first and rawRequest.q4_name.last separately.
Wrong field values Mapping wrong q{N} key Use the Test Webhook button to inspect the exact payload for your form. Field numbers are unique to each form and cannot be changed.
rawRequest is a string, not JSON Jotform sends it URL-encoded rawRequest arrives as a JSON string; parse it as JSON before reading fields. In WA.Expert, this is typically handled automatically by the webhook trigger.
Missing phone number Phone field not in form Add a Phone field to your Jotform form. After adding it, use Test Webhook to find its new q{N}_phone key.
Webhook fires on Preview submissions Using Preview mode for testing Jotform webhooks fire on Preview mode submissions too. Filter test data by checking submissionID patterns, or delete test entries from your form.

    
    Common questions
    What format does Jotform use for webhooks?+
Form-encoded POST. Each field is a q{N}_fieldname key. The rawRequest key contains all fields as a JSON string, which is easier to parse.
How do I find my form's field key names?+
Use the Test Webhook button in Jotform Settings → Integrations → Webhooks. Inspect the rawRequest JSON in WA.Expert's test mode.
Why does the Name field return an object?+
Jotform's Full Name field splits into first and last. Map rawRequest.q4_name.first and .last. Using a Short Text field gives a plain string.
Can I change the q{N} prefix?+
No. It is auto-assigned by field order and cannot be changed. Use Test Webhook to discover your exact keys.
Is Jotform's webhook available on the Free plan?+
Yes. Webhooks work on all Jotform plans including Free (5 forms, 100 submissions/month).
Does this incur extra WA.Expert charges?+
Each WhatsApp message uses a message credit. Utility: Rs. 0.14 on Starter, same Meta rates on Complete. No charge for receiving the webhook.

    
    Related guides
    Connect Typeform to WhatsApp
Typeform webhooks: typed answers array, field.ref mapping.
Read guide →
Connect Google Forms to WhatsApp
Google Forms via Apps Script onSubmit trigger.
Read guide →
External API Request Step
Master every field in WA.Expert's HTTP action step.
Read foundation guide →

Symptom	Likely cause	Fix
No webhook firing	Wrong URL or integration not saved	In Jotform Settings → Integrations → Webhooks, confirm the URL and status. Click Test to send a sample payload and verify receipt.
Empty name or garbled value	Mapping q4_name as string	The Full Name field is an object: {first, last}. Map rawRequest.q4_name.first and rawRequest.q4_name.last separately.
Wrong field values	Mapping wrong q{N} key	Use the Test Webhook button to inspect the exact payload for your form. Field numbers are unique to each form and cannot be changed.
rawRequest is a string, not JSON	Jotform sends it URL-encoded	rawRequest arrives as a JSON string; parse it as JSON before reading fields. In WA.Expert, this is typically handled automatically by the webhook trigger.
Missing phone number	Phone field not in form	Add a Phone field to your Jotform form. After adding it, use Test Webhook to find its new q{N}_phone key.
Webhook fires on Preview submissions	Using Preview mode for testing	Jotform webhooks fire on Preview mode submissions too. Filter test data by checking submissionID patterns, or delete test entries from your form.

Connect Jotform to WhatsApp

Step 1: Get your WA.Expert webhook URL

Step 2: Add the webhook in Jotform

Step 3: Understand the payload structure

Step 4: Discover your exact field keys

Worked example: contact form to WhatsApp alert

Troubleshooting

Common questions

Related guides

Connect Typeform to WhatsApp

Connect Google Forms to WhatsApp

External API Request Step

Connect Jotform to WhatsApp today