01Who this is for
- Businesses that automate order processing can link their shop directly to an agent, avoiding manual data entry.
- Support teams can fire a webhook when a ticket is raised, letting the agent locate the contact and add a note.
02Inbound webhook triggers, explained
An inbound webhook trigger is a special trigger type for Managed Agents. When an external system sends an HTTP POST request to the trigger’s URL, HighLevel starts the published agent and passes the request data as input. The agent reads the payload according to the instructions you provide and carries out actions such as finding a contact or creating a note.
The trigger lives inside AI Agents > Agent Studio. After you add the trigger, you configure a name, optional security, and the agent’s processing instructions. When the agent is published, the URL becomes active and can receive JSON, form data, XML, plain text or multipart requests. Execution details appear in the agent’s Activity Feed.
If the agent is unpublished or the trigger is deleted, the URL stops accepting requests. Duplicate requests are identified using an idempotency key, event ID or matching body, so the same run is not started twice.
03How businesses use inbound webhook triggers
- Ecommerce store. Create a trigger named New Order, paste the generated webhook URL into the store’s order webhook settings, and add the shared token header if verification is enabled. When a purchase occurs, the store posts order details and the agent creates an internal note with the order information.
- Subscription service. Add a Refund Requested trigger, configure the agent to locate the subscriber by email and generate a refund log entry. The service posts refund events to the trigger URL, and the agent processes each event automatically.
- Customer support platform. Set up a Ticket Created trigger that tells the agent to find the ticket requester and add a support note. The support tool posts new ticket data to the webhook, and the agent records the interaction in HighLevel.
04The numbers and rules that matter
- Supported request formats: JSON, form data, XML, plain text, multipart requests.
- Maximum payload: 256 KB.
- Request rate: Up to 60 requests per minute.
- Successful acceptance: HTTP 202 with a run ID.
- Duplicate protection: Recognizes supported duplicate requests via idempotency key, webhook event ID, or matching request body within a short period.
- Response codes: 202 accepted, 401 authentication failed, 404 webhook not found, 410 webhook unavailable, 413 request too large, 415 unsupported format, 429 too many requests.
05Before you start
- A Managed Agent must exist in AI Agents > Agent Studio, either as a draft or published version.
06How to set up and use inbound webhook triggers in HighLevel
Set up inbound webhook trigger
- Navigate to AI Agents > Agent Studio.
- Open an existing Managed Agent or create a new one.
- Enter the agent editor.
- In the Triggers pane, click Add trigger.
- Select Inbound webhook as the trigger type.
- Provide a descriptive name for the trigger, such as New Order.
- Add clear instructions that explain how the agent should use the incoming data.
- Open the inbound webhook trigger settings.
- Under Verification, choose Shared token header if authentication is required.
- Generate a shared token and copy it securely.
- Save the trigger settings.
- Save the agent and its trigger configuration.
- Publish the Managed Agent (the webhook URL is active only after publishing).
- In the inbound webhook settings, click Copy beside the Webhook URL.
- In the external application, open its webhook or HTTP request configuration.
- Set the request method to POST and paste the copied webhook URL.
- If verification is enabled, add the shared token to the request header.
- Send a test request from the external application.
- Return to the inbound webhook settings and check the Last request field.
- Open the linked execution to review the request and agent output.
- Use synthetic data or a test contact when testing agents that can send messages or update records.
07What it looks like in HighLevel
08Settings that matter
- Verification. Controls whether the inbound request must include a shared token header for authentication.
- Shared token header. The token value that external applications must send in either X Webhook Token or Authorization: Bearer header when verification is turned on.
09Things to know before you rely on it
- Request method must be POST.
- Maximum payload size is 256 KB.
- Request rate is limited to up to 60 requests per minute.
- Supported formats include JSON, form data, XML, plain text and multipart requests.
- Duplicate requests are recognized using an idempotency key, event ID or matching body within a short period.
10If something goes wrong
- Authentication failed (HTTP 401). Check that the shared token is correct and that it is sent in the required header.
- Request too large (HTTP 413). Reduce the size of the payload so it is under 256 KB.
- Unsupported format (HTTP 415). Make sure the request body matches one of the supported formats and that the Content Type header is set correctly.
- Too many requests (HTTP 429). Lower the request rate and respect any Retry After header in the response.
- Webhook not found (HTTP 404). Verify that the webhook URL is correct and has not been changed.
- Webhook unavailable (HTTP 410). Confirm that the Managed Agent is published and that the trigger is active.
11How it connects to the rest of HighLevel
- Learn the basics of workflow automation in HighLevel. Workflow basics
- View detailed steps for using inbound webhook triggers in Workflows. Workflow inbound webhook
- Check HighLevel pricing and plan options. Pricing
Michael's take

If I were wiring an online store to create order notes, I’d first publish the Managed Agent, copy the generated URL, enable token verification, and then send a test request with synthetic data. Once the Activity Feed shows a successful execution, I’d fine tune the instructions to pull the exact fields I need.





