What did HighLevel add for Jotform?
On September 20, 2026 HighLevel added native Jotform triggers and actions to GoHighLevel workflows. A workflow can now start the moment someone submits a Jotform form, start when a Jotform document with an e-signature is signed, and write workflow data back into a Jotform form as a new submission, without Zapier or another connector in between.
The source is HighLevel's changelog entry Jotform: New Actions and Triggers in Workflows. Until now, most businesses that collected intake forms, consent forms or applications in Jotform connected them to GoHighLevel through Zapier, Make or a webhook they built themselves. For a simple "form in, contact out" flow, that middle step is no longer needed.
Below: what the integration does, where it stops, and what we would change in an existing setup.
Which Jotform triggers and actions are available?
There are two triggers and one action. New Submission starts a workflow instantly when a form response arrives. New Signed Document starts a workflow when a document with an e-signature field is completed, and HighLevel checks for those every five minutes. Create Submission adds a new response to any form in your Jotform account, with values mapped from the workflow.
What the Jotform integration adds
| Piece | Type | When it runs | Typical use |
|---|---|---|---|
| New Submission | Trigger | Instantly on each response | Create the contact, tag the service, send the first reply |
| New Signed Document | Trigger | Checked every 5 minutes | Move a deal to "signed", start onboarding |
| Create Submission | Action | When the workflow reaches the step | Log a record in Jotform for teams that report there |
The five-minute check on signed documents is worth knowing. If your process sends a "thanks for signing" text, it will arrive within a few minutes, not seconds, which is fine for onboarding and too slow for anything a customer is waiting on while still on the page.
Which Jotform fields are supported?
Create Submission supports 15 field types: full name, email, address, phone, short text, long text, number, dropdown, single choice, multiple choice, yes/no, star rating, scale rating, date picker and time. File upload, signature, appointment, payment, product list, input table and several widgets are not supported, and HighLevel says unsupported fields save as empty.
Two formatting details from the changelog prevent quiet failures: dates must be sent as YYYY-MM-DD and times as HH:MM. If your GoHighLevel custom fields store dates in another format, add a formatting step before Create Submission, or the value will not land. The changelog lists these limits for the Create Submission action, so test your own form with a real response before relying on any field in the New Submission trigger either.
How do you connect Jotform to GoHighLevel?
In the workflow builder, add a Jotform trigger or action, click to connect your account and paste your Jotform API key, then pick the form; its fields load automatically. You can also connect from Settings, then Integrations, then Jotform, and reuse that connection in any workflow in the sub-account.
- Create an API key in your Jotform account settings, with a name that says which GoHighLevel sub-account uses it.
- Connect it once per sub-account.
- Build the trigger, then map each form field to a contact or custom field.
- Submit a test response and check the contact record, tags and pipeline stage.
- Only then switch off the old Zap or webhook that did the same job, so you do not create duplicates.
What does this change for your automation?
For simple form-to-CRM flows, you can remove a paid connector step and one more thing that can break. For flows that transform data, touch several apps or need file uploads and payments, keep the connector or a custom integration, because the native integration does not cover those fields.
Native trigger or connector?
The businesses that gain most are the ones where Jotform already holds the important paperwork: intake and consent forms at clinics and med spas, applications and agreements at agencies, job requests at home service companies. A signed agreement can now move the deal and start client onboarding on its own. If you are counting Zapier tasks, see our Zapier automation page for when a Zap is still the right tool, and our API integrations page for flows that need more than a form. For a real example of recurring paperwork moving without manual re-entry, see the Care Star Healthcare case study, and for clinic intake forms, our med spa page.
One caution for healthcare: if a form collects health information, check the business associate agreement terms of both Jotform and HighLevel for your plans before routing that data. Our guide to HIPAA and automation tools covers what to check.
Questions about the Jotform integration
Does the native Jotform integration replace Zapier?
For single form-to-contact flows, often yes. For flows that need filters across several apps, file uploads or payment fields, a connector or a custom build is still the better fit.
Will my existing Jotform Zaps stop working?
No. Nothing changes in Zapier. If you move a flow to the native trigger, turn the old Zap off after testing so each submission is not processed twice.
Can a Jotform signature trigger a GoHighLevel pipeline move?
Yes. Use the New Signed Document trigger and add an update-opportunity step. Expect up to five minutes of delay, because HighLevel checks for signed documents on that interval.
Sources and further reading
- HighLevel changelog, Jotform: New Actions and Triggers in Workflows, published September 20, 2026.
- Jotform, Jotform and HighLevel integration page.
