Home/HighLevel/Features/Workflows/How HighLevel works with Jotform triggers and actions

Workflows and Automation

How HighLevel works with Jotform triggers and actions

In short

The Jotform integration lets a HighLevel workflow start when a form is submitted or a signed document is completed, and it also allows a workflow to write data back into a Jotform form. It moves information between the two platforms without manual copying.

AreaWorkflows · Getting Started with Workflows
Used forReal estate brokerage, Insurance agency, Online course provider
Setup steps36 steps in 4 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Founders of service based businesses who collect client information via online forms and need automatic follow up.
  • Small agencies that require a signed contract to trigger internal processes such as onboarding.

02Jotform triggers and actions, explained

The integration adds Jotform as a source and destination inside the Workflow Builder. When a form response arrives, a webhook can fire a HighLevel workflow. For documents that contain e signatures, HighLevel polls Jotform every five minutes and starts the workflow once the signature is recorded. An action called Create Submission lets the workflow write values into a selected Jotform form.

All settings are accessed while building a workflow. The Jotform API key is entered during the connection step, after which the platform loads the list of available forms and the fields that can be mapped. The triggers and action behave according to their delivery method, webhook for new submissions and polling for signed documents, and they expose the supported field types for mapping.

03How businesses use Jotform triggers and actions

  • Real estate brokerage. The brokerage creates a Jotform for property viewing requests. When a visitor submits the form, the New Submission trigger starts a workflow that assigns the lead, sends a follow up email, and logs the request in HighLevel.
  • Insurance agency. The agency uses Jotform to collect policy applications that include an e signature. The New Signed Document trigger polls for the completed signature, then launches a workflow that creates a policy record and notifies the underwriting team.
  • Online course provider. After a student completes a registration form in HighLevel, the provider adds a Create Submission action that writes the student's details into a Jotform used for offline attendance tracking.

04The numbers and rules that matter

  • Create Submission supports 15 standard Jotform input types.
  • Supported fields: Full Name, Email, Address, Phone, Short Text, Long Text, Number, Dropdown, Single Choice, Multiple Choice, Yes/No, Star Rating, Scale Rating, Date Picker, Time.
  • Unsupported fields: File Upload, Signature, Appointment, Payment, Product List, Input Table, Fill in the Blanks, Spinner, Emoji Slider, Image Choice, Captcha, Widgets (including Terms and Conditions, Checklist, Configurable List, Multi Text List, Dynamic Text Box, and Calculation).

05Before you start

  • A Jotform account must be linked to the specific HighLevel subaccount.
  • The Jotform API key is required for the connection.

06How to set up and use Jotform triggers and actions in HighLevel

Connect Jotform from Workflow Builder

  1. Open Automation > Workflows from the Subaccount view.
  2. Start a new workflow or edit an existing one.
  3. Select Add New Trigger for a trigger or the + button for an action location.
  4. Search the catalog for Jotform.
  5. Choose the needed Jotform trigger or action.
  6. If no account is linked, click Connect your account.
  7. Enter the Jotform API key and finish the connection.

Set up a New Submission trigger

  1. Navigate to Automation > Workflows and open or create a workflow.
  2. Click Add New Trigger.
  3. Search for Jotform and pick New Submission.
  4. Link the Jotform account if it is not already linked.
  5. Provide a name for the trigger and fill in the required settings.
  6. Select the form that will generate the submission event.
  7. Press Test Trigger and examine the sample data returned.
  8. Save the trigger configuration.
  9. Add the subsequent workflow actions and publish when ready.

Set up a New Signed Document trigger

  1. Go to Automation > Workflows and open or create a workflow.
  2. Click Add New Trigger.
  3. Search for Jotform and select New Signed Document.
  4. Connect the Jotform account if needed.
  5. Enter a trigger name and complete the required fields.
  6. Choose the form or document that contains the e signature field.
  7. Click Test Trigger to pull available metadata.
  8. Save the trigger.
  9. Add downstream actions and publish the workflow.

Add a Create Submission action

  1. Open Automation > Workflows and edit the target workflow.
  2. Click the + button at the point where the Jotform action should run.
  3. Search for Jotform.
  4. Select Create Submission from the results.
  5. Connect the Jotform account if it is not already linked.
  6. Pick the destination Jotform form for the new submission.
  7. Allow HighLevel to retrieve the list of supported fields.
  8. Map each field using static text or a workflow custom value.
  9. Apply YYYY MM DD format for date fields and HH:MM for time fields.
  10. Review the mappings and save the action.
  11. Publish the workflow when the automation is complete.

07What it looks like in HighLevel

08Settings that matter

  • Jotform API key. Identifies the Jotform account that HighLevel will use for triggers and actions.

09Things to know before you rely on it

  • A Jotform account must be linked before any trigger or action can run.
  • New Submission uses a webhook and fires immediately; New Signed Document relies on polling roughly every five minutes, so a short delay may occur.
  • Create Submission can only populate 15 standard Jotform input types; unsupported fields are omitted and left empty.
  • Required fields that are unsupported are still left blank without causing an error in the workflow.
  • The action does not generate payments, signatures, or appointment reservations.

10How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

The first thing I would get right is the Jotform connection itself. Make sure the API key is entered and the account is linked before you start building any triggers.

Once the connection is solid, I would set up a New Submission trigger for any lead capture form and immediately test it so the metadata shows up. That way the rest of the workflow can pull values like email or phone without extra steps.

Get More InformationOpens on HighLevelPublished November 3, 2026 · Updated November 17, 2026

Common questions

Common questions about Jotform triggers and actions.

Why does a signed document trigger take longer to fire?

The New Signed Document trigger uses polling. HighLevel checks Jotform about every five minutes, so a brief delay between the signature and workflow start is normal.

What is the purpose of testing the trigger during setup?

Running Test Trigger pulls sample metadata from Jotform, making the submission values available for later steps in the workflow.

Why might a field from my Jotform form not appear in the Create Submission mapping list?

Only the supported field types are shown. Fields such as File Upload, Signature, Appointment, Payment, and others are unsupported and therefore omitted.

What happens if a required field in Jotform is unsupported by Create Submission?

Create Submission leaves that field empty, but Jotform still accepts the submission and marks it as active, and the workflow does not generate an error.

Can Create Submission generate a signature for a signed document form?

No. The trigger can detect that a document has already been signed, but Create Submission cannot populate a signature field.

Does Create Submission register a payment or appointment when used with a payment or appointment form?

No. The action does not process payments, attach amounts, generate signatures, or reserve appointment slots.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.