Inbound and outbound webhooks

Webhooks move data between HLB and your other systems automatically. An inbound webhook brings data in and starts a workflow. An outbound custom webhook sends data to another service when a contact reaches a workflow step.

For a local service business, an inbound webhook can capture leads from a form on another website, record orders from an online store, or bring in support tickets or event registrations. The contact and details then appear in your CRM without manual entry. An outbound webhook can send contact or job details to a tool you already use.

Inbound webhook trigger:

• Add the Inbound Webhook trigger to a workflow and copy its URL into your other system.
• Send data to the URL using POST, GET or PUT, click Test Trigger, and pick the sample request to save as your mapping reference.
• In the Create Update Contact action, map the incoming fields. An email or phone number is required.
• Use the incoming values in emails, texts, if/else branches and other actions.

Custom webhook action:

• Enter the destination URL and choose POST, GET, PUT or DELETE.
• Pick an authorization method and add headers and query parameters as needed.
• Build the request body from custom values (including inbound webhook values), with suggestions as you type.

The outbound action fires as soon as a contact reaches the step, and it only succeeds if the receiving server responds successfully. Errors can make the action fail or retry, so make sure the receiving system can handle the number of requests you'll send.