> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/triggers-and-http/webhook.md).

# Webhook

### Overview

The Hablla platform Webhook component is used to kick off automated flows based on external events. It acts as an entry point, receiving data via HTTP requests (usually POST) and triggering the corresponding flow immediately.

***

### Main Functionality

* 🔄 Real-time integration with external systems\ <br>
* 🔧 Automatic triggering of flows\ <br>
* ✅ Immediate execution after receiving the data\ <br>
* 📁 Transmission of structured data (JSON)\ <br>

***

### How the Webhook Works

In the provided image, we have two examples of webhook execution:

#### Example 1 – Execution with Code and POST

1. Webhook (IMMEDIATELY): The component receives an external request with data (e.g., CRM, forms, ERPs, etc.).\ <br>
2. Code: A code block is executed right afterward. This can process, handle, or transform the received data.\ <br>
3. HTTP Request (POST): The processed data is sent to another system or service via a new HTTP request.

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXdv40lAbKoEOW5_FBQ_hNT5LDYcqgk7JvF3v6B8kx5GupTct8po6J1Objw0csyPftPuk--bWxJtHPSAvxUlf7eSTeUexBTLWr_Sfm17aSFCVpULYNiohjaGrntrv9T--nm68bTpnA?key=sgLkhO3rLtu4xk-SUxqLWQ)

#### Example 2 – Execution with Formatting, Creation and Sending of HSM

1. Webhook (IMMEDIATELY): Receives the lead's or customer's data.\ <br>
2. Format Phone: The received phone number is standardized to the international format required for sending via WhatsApp.\ <br>
3. Hablla (CREATE\_OR\_UPDATE): Creates or updates the person within Hablla's CRM with the received data.\ <br>
4. WhatsApp HSM: After registration, a template (HSM message) is automatically sent to resume contact with the customer.

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXehdYtgA0dsBK0gYOwvR9AV559oNyFSEx-MeX3ddtRer6wlBQgNbT6kE_-7D344Gxrogsk1-p2gbjrUxmZpp1r_B6jReXkSVXtDyHk5J6PJvy71JFzebLRPmOsSa7Z0rsuuCyEZNw?key=sgLkhO3rLtu4xk-SUxqLWQ)\ <br>

***

### Main Use Cases

* ✨ Integration with ERPs and CRMs\ <br>
* 🚀 Automatic triggering of flows from landing pages or forms\ <br>
* 📊 Sending data to BI or monitoring systems\ <br>
* 🛠️ Updating records or leads\ <br>
* 💬 Automatic reengagement with leads via HSM (WhatsApp Template)\ <br>

***

### Benefits

* ⏱ Instant execution\ <br>
* 🛑 Reduction of manual errors\ <br>
* 📊 Standardization in data reception\ <br>
* 🚀 Ability to scale integrations quickly\ <br>

***

### Webhook Request Example

POST <https://webhook.hablla.com/v1/682f73fc0a50>...........

{

&#x20; "name": "João Silva",

&#x20; "email": "<joao@email.com>",

&#x20; "phone": "11999998888"

}

This webhook triggers a flow that, upon receiving the data, formats the phone number, creates or updates the contact within Hablla and sends a message via WhatsApp (HSM) to resume engagement with the lead.

***

The webhook component is ideal for operations that require immediate response to external events, promoting effective, reliable, real-time integrations.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/triggers-and-http/webhook.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
