Resources · n8n integration

Jotform n8n integrationAutomate Jotform with n8n.

Every Jotform submission can start a workflow instead of an email thread. The Jotform n8n integration ships one trigger node, version 1, with 3 settings and no action node. It listens to a single form and hands the answers to the rest of your workflow. Built for teams drowning in form replies.

Try the Jotform integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Jotform n8n integration actually do?

Jotform in n8n is a one way street, and that is the whole point. The catalog gives you a trigger node and 0 operations, so n8n never writes back to Jotform. What it does is catch each submission the moment it happens, turn the raw payload into named fields, and pass it to whatever comes next in the workflow: a spreadsheet, a chat message, a model, a database.

Start with the simplest shape. A visitor fills your form, the trigger fires, and a Google Sheets node appends a row with the answers already labeled. No export, no weekly download, no copy paste. The sheet becomes the log that sales or ops actually open.

Second shape: routing. Sales leads land in Slack as a formatted message in the channel that owns them, while a Gmail node sends the person who submitted a real acknowledgment with their own answers quoted back. Both branches run from the same trigger, so nothing falls between two tools.

Third shape: sorting before storing. Free text answers go through OpenAI to get a category and a short summary, then an Airtable node files the record with that category already set. Support requests stop arriving as one undifferentiated pile.

When the nodes stop, HTTP Request takes over. There is no Jotform action node, so anything that reads or writes on the Jotform side, listing forms or pulling older submissions, goes through the HTTP Request node. It calls any endpoint of the Jotform API and reuses the same credential through predefined authentication, so you do not manage a second key.

Know the limits before you build. The trigger watches one form, chosen in Form Name or ID, so several forms means several triggers or several workflows. There is no event list to pick from: a submission is the only thing that fires it. And the webhook is registered with Jotform when the workflow is activated, which means a workflow left inactive receives nothing. If you are still choosing a platform, the n8n review goes through that trade off in detail.

Connect

How do you connect Jotform to n8n?

  1. 01

    Create the API key in Jotform

    In Jotform, open Settings then API, and select Create New Key. Select the Name in Jotform to rename the key into something you will recognize later, for example n8n integration. Naming matters more than it looks: keys are easy to create and impossible to tell apart six months later when you want to revoke one.

  2. 02

    Store the credential in n8n

    In n8n, go to the Credentials menu and create a Jotform credential. A credential is the saved authentication that nodes reuse, so you set it up once and every workflow picks it from a dropdown. Paste the API Key you copied into the field of the same name. The trigger node then offers that credential without asking for the key again.

  3. 03

    Pick the right API domain

    The credential also asks for the API Domain, and the value depends on the forms you use. Choose api.jotform.com unless one of the other cases applies. Pick eu-api.jotform.com if your forms are Jotform EU Safe Forms, and hipaa-api.jotform.com if they are HIPAA forms. Save, then open the trigger and select your form.

Triggers

What starts a Jotform workflow?

Jotform Trigger is the node that starts a workflow each time Jotform receives a new submission. Pick the form, activate the workflow: n8n registers the webhook on your Jotform account.

What you see in n8n

Configuration notes

01Set Up the Jotform TriggerThe trigger listens to one Jotform form and starts the workflow each time someone submits it. A trigger is the node that opens a workflow, and this one runs on a webhook, a URL that n8n exposes and Jotform calls. n8n registers that URL with Jotform when the workflow is activated, so a submission reaches the workflow in seconds, with no polling and no schedule to tune.

The trigger listens to one Jotform form and starts the workflow each time someone submits it. A trigger is the node that opens a workflow, and this one runs on a webhook, a URL that n8n exposes and Jotform calls. n8n registers that URL with Jotform when the workflow is activated, so a submission reaches the workflow in seconds, with no polling and no schedule to tune.

Key parameters

  • Form Name or ID: required. Choose the form from the list, or specify an ID using an expression such as {{ $json.formId }}. An expression is how n8n injects a value coming from an earlier node into a field.
Use cases
a quote request form on a landing page that feeds the whole follow up chain, from the notification to the record.
When to use it
whenever the submission itself is the event you care about. For anything you need to fetch later, the HTTP Request node is the route.
02Resolve DataRaw webhook data from Jotform uses internal keys instead of the question names, which makes a mapping painful to read and worse to maintain. Resolve Data fixes that at the source: activate it and n8n resolves the keys automatically to the actual names, so the fields arriving in the workflow carry the labels you gave your questions.

Raw webhook data from Jotform uses internal keys instead of the question names, which makes a mapping painful to read and worse to maintain. Resolve Data fixes that at the source: activate it and n8n resolves the keys automatically to the actual names, so the fields arriving in the workflow carry the labels you gave your questions.

Key parameters

  • Resolve Data: a boolean, off by default. Activated, the internal keys become the real question names, and your expressions read like the form itself.
Use cases
a registration form whose answers go straight into named spreadsheet columns, where a mapping built on internal keys would break the day you reorder the questions.
When to use it
as a default on any form you will map field by field.
03Only AnswersA Jotform webhook carries more than what the visitor typed. Only Answers strips the rest: activated, the trigger returns only the answers of the form and not any of the other data, so each execution starts from a clean item instead of a payload you have to dig through.

A Jotform webhook carries more than what the visitor typed. Only Answers strips the rest: activated, the trigger returns only the answers of the form and not any of the other data, so each execution starts from a clean item instead of a payload you have to dig through.

Key parameters

  • Only Answers: a boolean. Activated, only the answers come through. Left off, the full webhook payload reaches the workflow.
Use cases
a survey feeding a model, where the extra metadata adds tokens and noise for no gain. The same goes for a short form whose answers go straight into a chat message, since nobody reads the submission envelope.
When to use it
leave it off while you inspect a first execution and see what Jotform actually sends, then activate it once you know which fields you keep.
Need help

Need help automating Jotform with n8n?

A person reads every message.

FAQ

Jotform and n8n, the questions that come next

01Is the Jotform n8n integration free?
Yes on the n8n side. The Jotform trigger node ships with n8n, so there is nothing to install and nothing extra to pay for the node itself. It behaves the same on n8n Cloud, the hosted offer run by n8n, and on a self hosted instance installed through Docker or npm under the Community Edition and its Sustainable Use license. A workflow built on one runs on the other without changes. What a Jotform account costs is a separate question, and this page does not cover it. The one thing to plan for is the API key, which requires an account able to create keys in the Jotform settings.
02What credentials do you need to connect Jotform to n8n?
One credential, built on an API key. The Jotform trigger supports a single authentication method: you create the key in Jotform under Settings then API with Create New Key, rename it to something meaningful, and paste it into the API Key field of the n8n credential. The credential also needs the API Domain, and the right value depends on your forms: api.jotform.com in the standard case, eu-api.jotform.com for EU Safe Forms, hipaa-api.jotform.com for HIPAA forms. A credential is created once in the Credentials menu and reused by every workflow, so a second Jotform trigger picks it from the dropdown.
03What are the limits of Jotform in n8n?
The main one is that nothing goes back to Jotform. The catalog has 0 operations and no action node, only the trigger, so n8n reads submissions as they arrive and never creates or edits a form. Anything on the Jotform API beyond that, listing forms or fetching earlier submissions, goes through the HTTP Request node, which reuses the same credential through predefined authentication. The trigger itself also watches a single form, set in Form Name or ID, so covering several forms means several triggers. And since the webhook is registered when the workflow is activated, an inactive workflow receives nothing at all.
04Does the Jotform trigger react in real time?
Yes, it works on a webhook. n8n exposes a URL and registers it with Jotform when you activate the workflow, then Jotform calls that URL on each submission, so the execution starts within seconds. There is no polling interval to configure and no delay to compensate for, which also means no wasted executions when nobody submits anything. Two practical consequences. The workflow has to be active for the webhook to exist, so a draft left inactive collects nothing. And there is no event list to choose from: a form submission is the only thing that starts this trigger.
05n8n or Make for Jotform forms?
It depends on where your data has to live and how you want to pay. Make is a hosted automation platform with no self hosting option, billed per operation, which suits a small volume of submissions handled with little setup. n8n runs on its own Cloud or on your own server through Docker or npm, so form answers, which often carry personal data, can stay on infrastructure you control, and the cost model does not follow the number of submissions. The visual logic differs too, n8n being closer to a data flow you branch and debug execution by execution. For Jotform in particular, both sides reach the same webhook.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations