Jotform Automation in GoHighLevel: New Workflow Triggers and Actions

Jotform Automation inside GoHighLevel now gives you more direct control over what happens when someone fills out a form or signs a document.

The first new option is the New Submission trigger. This starts a GHL workflow when someone sends a new response through a connected Jotform form. That means you can move a lead into follow-up right away without importing the data by hand.

The second option is the New Signed Document trigger. This starts a workflow when someone completes and signs a Jotform document that includes an e-signature field. HighLevel checks for these signed documents every five minutes.

The third addition is the Create Submission action. This works in the other direction. Instead of waiting for someone to fill out a Jotform, your GHL workflow can create a new Jotform submission using data already available inside the workflow.

Together, these tools make Jotform Automation much more useful inside GHL. You can now bring Jotform activity into HighLevel and also send selected workflow data back into Jotform.

This creates a cleaner connection between your forms, CRM, follow-up, onboarding, and reporting. It also gives you more ways to build automations without relying on extra tools for every step.

Jotform Automation can save time because it removes steps that used to need manual work or extra tools.

For example, a new Jotform lead can now start a GHL workflow right away. You can send a reply, add a tag, update the contact, or notify your sales team without waiting for someone to move the data by hand.

It can also help with client onboarding. When a signed Jotform document comes in, HighLevel can start the next part of the process. You could update a pipeline stage, create a task, notify your team, and send the client their next steps.

This update is also useful for offline leads. If someone signs up by phone, at an event, or in person, a GHL workflow can create a matching Jotform submission. That helps keep more of your lead data in one place.

Another benefit is that you may be able to use fewer third-party tools. In some setups, this could replace a zap, webhook, or manual transfer between Jotform and GHL.

That matters because fewer tools usually means fewer things to break.

For agencies, this can also make client systems easier to manage. You can build cleaner workflows, reduce repeated admin work, and keep important actions moving in the background.

Setting up Jotform Automation in GoHighLevel starts inside the Workflow Builder. You will connect your Jotform account, choose the trigger or action you want to use, and then select the Jotform form that will work with your automation.

Once your account is connected, HighLevel loads the available fields from the selected form. You can then map those fields to information inside your workflow. This gives you a direct way to start workflows from Jotform activity or create new Jotform submissions from GHL.

Here are the steps you will follow:

• Access the Workflow List page in GoHighLevel
• Open the Workflow Builder
• Add a Jotform Trigger or Action
• Connect Your Jotform Account
• Select Your Jotform Form
• Map the Jotform Fields
• Save and Publish Your Workflow

To start make sure you are logged in to your GoHighLevel sub-account.

The Main Menu on the left side of your screen includes the main areas you work in when using GHL.

1.1 Click the Automation main menu item.

• This opens the Automation area of your GoHighLevel sub-account.
• Inside this area you can access your workflows and other automation tools.

1.2 Click Workflows in the top menu if the Workflow List page is not already showing.

• The Workflow List page contains your existing workflows and workflow folders.
• You can open an existing workflow or create a new workflow from this page.

2.1 Open the workflow you want to use for your Jotform Automation.

• Click an existing workflow from the Workflow List page.
• If you are building a new automation, create a new workflow instead.
• Opening the workflow takes you into the Workflow Builder.

The Workflow Builder is where you choose what starts the automation and what happens after it starts.

2.1 Click the area where you want to add your Jotform trigger or action.

• For a Jotform event that will start the workflow, add a new workflow trigger.
• For a Jotform task that should happen during the workflow, add a new workflow action.
• A new selection section will open.

2.2 Search for Jotform.

• Type Jotform into the search field.
• HighLevel will display the available Jotform options.

2.3 Select the Jotform trigger or action you want to use.

For triggers, the current options include:

• New Submission – Starts the workflow when someone submits a new response through the selected Jotform form.
• New Signed Document – Starts the workflow after a Jotform document with an e-signature field has been completed and signed.

For actions, the current option is:

• Create Submission – Creates a new submission inside a selected Jotform form using information from your GHL workflow.
• Choose the option that matches what you want the workflow to do.
• The Jotform setup section will open after you make your selection.

You need to connect Jotform before HighLevel can access your forms.

3.1 Click Connect your account.

• HighLevel will open the Jotform connection process.
• You will be asked to provide the information needed to connect your Jotform account.

3.2 Provide your Jotform API key.

• Follow the prompts shown during the connection process.
• Enter the API key from the Jotform account you want to use.
• Make sure you connect the correct Jotform account if you manage forms for more than one business.

3.3 Complete the account connection.

• After the connection is accepted, HighLevel will make your Jotform account available inside the workflow.
• You can now choose a Jotform form.

You can also connect Jotform before building the workflow.

Go to Settings → Integrations → Jotform and connect the account there. After the connection is complete, return to the Workflow Builder and continue with the steps below.

4.1 Click the Jotform form selection field.

• HighLevel will display the forms available from your connected Jotform account.
• If your expected form does not appear, first confirm that you connected the correct Jotform account.

4.2 Select the form you want this workflow to use.

• For New Submission, choose the form whose new responses should start the workflow.
• For New Signed Document, choose the form or document connected to the signed-document process.
• For Create Submission, choose the form where HighLevel should create the new submission.
• Once you select the form, HighLevel automatically loads the supported fields available for mapping.

Field mapping tells HighLevel which workflow information should be placed into each supported Jotform field.

6.1 Review the Jotform fields that appear after selecting your form.

• HighLevel only shows field types currently supported by the Create Submission action.
• Unsupported fields will not appear in the mapping list.

6.2 Click the field you want to map.

• Select the matching information from your GoHighLevel workflow.
• For example, you could map the contact’s name to the Jotform Full Name field.
• You could map the contact’s email address to Email.
• You could map the contact’s phone number to Phone.

6.3 Continue mapping each field needed for the submission.

• Only map fields that your workflow actually needs.
• Check each field carefully so the correct GHL information is sent to the correct Jotform field.

Supported fields currently include:

• Full Name.
• Email.
• Address.
• Phone.
• Short Text.
• Long Text.
• Number.
• Dropdown.
• Single Choice.
• Multiple Choice.

Jotform Automation becomes most useful when you connect a form event to work that normally needs someone to step in.

Instead of simply collecting information, you can use each Jotform submission to start the next part of your sales, onboarding, or customer process inside GoHighLevel.

Here are four strong ways to use this update.

Lead Capture and CRM Follow-Up

A new lead fills out your Jotform website form.

The New Submission trigger can start a GHL workflow as soon as that response arrives.

Your workflow could then:

• Create or update the contact in your CRM.
• Add a New Lead tag.
• Send an email or SMS confirmation.
• Create an opportunity in your sales pipeline.
• Notify your sales team.
• Start your lead nurturing sequence.

This removes the need to manually move Jotform leads into your follow-up system.

Signed Contract to Client Onboarding

You can also use Jotform Automation to move a new client from signing to onboarding.

When the client signs a Jotform document, the New Signed Document trigger can start your onboarding workflow.

That workflow could:

• Move the opportunity to Contract Signed.
• Send the client a welcome message.
• Create an onboarding task for your team.
• Notify your operations staff.
• Send instructions for the client’s next step.

Remember that HighLevel checks for newly signed Jotform documents every five minutes, so this trigger may not fire the exact second the document is signed.

Offline Sign-Up to Jotform

Not every lead comes through an online form.

Someone may register over the phone, at an event, or while speaking with your team.

You can use the Create Submission action to send that contact information from GHL into the matching Jotform form.

This helps keep your Jotform reporting more complete because your online and offline registrations can appear in the same place.

Appointment to Intake Form

Another useful Jotform Automation starts when someone books an appointment in GoHighLevel.

Your workflow could use the Create Submission action to create a Jotform entry using information already stored in the contact record.

For example, you could send:

• The client’s name.
• Email address.
• Phone number.
• Appointment-related information.
• Other supported contact details.

This can reduce repeated data entry and prepare part of the intake process before your team starts working with the client.

The main idea is simple. Look for places where your team is copying information, watching for submissions, or waiting for someone to complete the next task.

Those are usually the best places to put Jotform Automation to work.

Jotform Automation works well, but not every Jotform field can be used with the Create Submission action.

Before you build the workflow, check which fields are supported. This will help you avoid missing data or failed expectations.

Supported Jotform Fields

HighLevel currently supports these Jotform field types for Create Submission:

• Full Name.
• Email.
• Address.
• Phone.
• Short Text.
• Long Text.
• Number.
• Dropdown.
• Single Choice.
• Multiple Choice.
• Yes/No.
• Star Rating.
• Scale Rating.
• Date Picker.
• Time.

These supported fields will appear when you map data inside the workflow.

Unsupported Jotform Fields

Some field types do not appear in the mapping list.

These include:

• File Upload.
• Signature.
• Appointment.
• Payment.
• Product List.
• Input Table.
• Fill in the Blanks.
• Spinner.
• Emoji Slider.
• Image Choice.
• Captcha.
• Terms and Conditions.
• Checklist.
• Other unsupported widgets.

If one of these fields is part of your Jotform, HighLevel will leave that field empty when the submission is created.

This can still happen even if the field is marked as required inside Jotform.

Watch Out for Payment Forms

The Create Submission action does not collect payment.

If you use it with a payment form, the new submission can look similar to a paid submission inside Jotform.

That means you should not treat the record as paid unless payment was collected through another process.

Signatures Work Differently

The New Signed Document trigger can detect a document that has already been signed in Jotform.

But the Create Submission action cannot create or add a signature.

A real person must still complete the signature inside Jotform.

Use the Correct Date and Time Format

When mapping date and time fields, use the correct format.

• Dates use YYYY-MM-DD.
• Times use HH.

This helps prevent mapping issues and keeps the submission data clean.

HighLevel has also stated that more Jotform field types are expected to be supported in future releases. For now, the safest approach is to build your workflow around the supported fields listed above.

Jotform Automation can save a lot of time, but a few small setup mistakes can cause bad data or confusing results.

Use these tips before you publish your workflow.

Test the Workflow Before You Go Live

Run a test submission before sending real leads through the workflow.

Check that:

• The correct Jotform form is selected.
• The right workflow starts.
• Each mapped field sends the correct information.
• Your follow-up actions run in the right order.
• Your team notifications go to the right place.

A two-minute test can save you from cleaning up bad data later.

Be Careful with Payment Forms

The Create Submission action does not collect payment.

If you create a submission on a Jotform payment form, do not assume the person has paid. The submission may still appear active even though no payment was collected.

Use a separate payment check before moving someone into a paid or completed stage.

Do Not Try to Map Signatures

The Create Submission action cannot add a signature.

If a signature is required, the person still needs to complete that step inside Jotform.

Use the New Signed Document trigger after the real signature has been completed.

Keep Your Field Mapping Simple

Only map the fields you actually need.

Extra mapping can make a workflow harder to manage and easier to break. Start with the main contact details, then add more fields only when they serve a clear purpose.

Use the Correct Date and Time Format

For date fields, use YYYY-MM-DD.

For time fields, use HH.

Keeping the format correct helps prevent bad values from being sent into Jotform.

Name Your Workflows Clearly

Use workflow names that explain exactly what the automation does.

For example:

• Jotform – New Lead Follow-Up
• Jotform – Signed Contract Onboarding
• Jotform – Appointment Intake Submission

Clear names make it much easier to manage workflows later, especially if you run many client accounts.

Remember the Five-Minute Check

The New Signed Document trigger checks for signed documents every five minutes.

So do not build a process that depends on the trigger firing the exact second a contract is signed.

A short delay is normal.

Watch for Unsupported Fields

Unsupported fields do not appear in the mapping list.

If a field is missing, check whether that field type is supported before troubleshooting the connection.

This is especially important for fields like Signature, Payment, File Upload, and Appointment.

The best approach is simple. Build the workflow with supported fields, test it fully, and keep the setup easy to manage.

Jotform Automation can help your business move faster without adding more manual work.

Instead of waiting for someone to copy form data, check for signed documents, or move information between systems, you can let the workflow handle those steps for you.

That can make a big difference when your business handles a lot of leads, clients, appointments, or onboarding tasks.

For lead generation, a new Jotform submission can move straight into your GHL follow-up process. Your team can respond faster, add the right tags, create opportunities, and start nurturing without waiting for someone to update the CRM.

For client onboarding, a signed document can trigger the next part of the process. That means your team can move from contract to onboarding with fewer delays.

It can also help keep your data cleaner. If you collect leads by phone, at events, or through other offline methods, you can create Jotform submissions from GHL and keep more of your records together.

Another big benefit is fewer tools.

In some setups, this direct connection can reduce the need for extra zaps, custom webhooks, or manual data transfers.

Fewer tools can mean:

• Lower software costs.
• Fewer failure points.
• Easier troubleshooting.
• Simpler client systems.
• Less time spent fixing broken connections.

For agencies, this can also make your automations easier to manage across multiple client accounts.

The real value of Jotform Automation is not just that it connects two platforms. It helps you build a smoother process from lead capture to follow-up, onboarding, and reporting.

Jotform Automation gives GoHighLevel users a cleaner way to connect forms, signed documents, and workflow actions.

The new New Submission trigger can start follow-up as soon as a form is submitted. The New Signed Document trigger can move clients into onboarding after they sign. The Create Submission action can also send workflow data back into Jotform.

That means less manual data entry, faster follow-up, and fewer steps for your team to manage.

For agencies, this can also make client systems easier to build and maintain. You may be able to replace some third-party zaps or webhooks with a direct connection between Jotform and GHL.

Just remember the current limits. Not every Jotform field is supported, payment data is not created, signatures cannot be written by the Create Submission action, and signed documents are checked every five minutes.

The best way to start is with one simple workflow. Connect one form, map the main fields, test the process, and make sure the data goes where you expect.

Then build from there.

The team here at GHL Growth Garage will keep breaking down new GoHighLevel updates into practical guides you can use in your own account.

Have you tried Jotform Automation in GHL yet? What process are you planning to automate first?