Home/HighLevel/Features/Workflows/How to set up the Inbound Webhook trigger in HighLevel

Workflows and Automation

How to set up the Inbound Webhook trigger in HighLevel

In short

The Inbound Webhook Trigger lets a HighLevel workflow start when it receives a POST, GET, or PUT request at a unique URL. The trigger captures the incoming JSON data, which can then be mapped to workflow fields and used to run automated actions.

AreaWorkflows · Developer Resources
Used forEcommerce store, Subscription SaaS company, Medical clinic
Setup steps7 steps in 1 task
Last updatedNovember 16, 2026

01Who this is for

  • SaaS Founders who need real time payment notifications to keep lead records current.
  • Ecommerce owners who want order data from external checkout systems to start follow up sequences.
  • Service based businesses that receive appointment confirmations from third party calendars and wish to update client statuses automatically.

02Inbound webhook triggers, explained

The Inbound Webhook Trigger starts a HighLevel workflow whenever an external application sends a POST, GET, or PUT request to a generated URL. The request can contain any JSON payload, such as form submissions or payment updates. Once the data arrives, the workflow can use it to drive actions like status changes or email sends.

The trigger appears in the workflow editor. After selecting it, HighLevel creates a unique webhook address that you copy and give to the outside service. The workflow then lets you map any incoming JSON fields to internal variables, enabling precise automation based on the received data.

You find this feature inside any workflow under the trigger selection area. Choose Inbound Webhook, copy the URL, configure the external app, test, map fields, and save the trigger to activate the integration.

03How businesses use inbound webhook triggers

  • Ecommerce store. Create a workflow that uses the Inbound Webhook Trigger. Provide the generated URL to your checkout platform so it posts order details in JSON. Map the order fields to workflow variables and automatically send order confirmation emails.
  • Subscription SaaS company. Set up the webhook trigger and give the URL to your payment processor. When a subscription payment succeeds, the processor posts the payment data. The workflow maps the payment status and updates the customer record, then sends a receipt email.
  • Medical clinic. Add the Inbound Webhook Trigger to a workflow and share the URL with an online scheduling tool. The tool posts appointment data when a patient books. Map the appointment fields to the clinic's lead record and trigger reminder messages.

04How to set up and use inbound webhook triggers in HighLevel

Set up inbound webhook trigger

  1. Open an existing workflow or create a new one in HighLevel.
  2. Select the Inbound Webhook option as the workflow trigger.
  3. Copy the unique webhook URL that HighLevel generates for the trigger.
  4. In the external application, configure a POST request that points to the copied URL and includes the required JSON payload.
  5. Send a test request from the external application to verify the webhook reaches HighLevel.
  6. In the workflow editor, map the incoming JSON fields to the desired workflow variables or fields.
  7. Click the Save Trigger button to finalize the configuration.

05What it looks like in HighLevel

06Settings that matter

  • Inbound Webhook. Determines that the workflow will listen for incoming POST, GET, or PUT requests at a generated URL and provides that URL for external integration.

07Things to know before you rely on it

  • The article does not specify any limits, exclusions, or beta status for this trigger.

08How it connects to the rest of HighLevel

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 16, 2026

Common questions

Common questions about inbound webhook triggers.

What HTTP methods does the Inbound Webhook Trigger accept?

It captures POST, GET, or PUT requests sent to the generated webhook URL.

How is the webhook URL created for a workflow?

When you select Inbound Webhook as the trigger, HighLevel automatically generates a unique URL that you copy for use in external applications.

Can I map data from the incoming webhook to workflow variables?

Yes, after the webhook fires you can select the incoming data and map it to fields or variables inside the workflow.

Is the Inbound Webhook Trigger available for any workflow in HighLevel?

The article indicates it can be selected as a workflow trigger for any workflow you create in HighLevel.

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.