# Webhook

{% hint style="success" %}
A webhook is a method used to automatically **transfer data** from NeoDove to another application as it happens in **real-time**. 
{% endhint %}

Essentially, it is a way for NeoDove to provide other applications with real-time information. 

Webhooks are typically used to **notify** your system of an event or change that occurred, without the need for your **system** to constantly poll for updates.

### Here’s how it works:

***

1. **Setup:** You configure a NeoDove webhook by providing a URL endpoint on any of your particular software's or application's server where you want to receive data.
2. **Trigger:** An event occurs in the source application (e.g., a new lead gets created or updated, an order is placed, a payment is processed).
3. **Notification:** NeoDove makes an HTTP request (usually a POST) to the webhook URL, sending data about the event in the requested application.
4. **Processing:** Your particular application's server receives the data and processes it according to your needs (e.g., updating a database, sending a notification, triggering a workflow).

### Example:

***

Imagine you have an **e-commerce website** and you want to keep your inventory system updated in **real-time** when an order is placed. You can set up a **webhook** in your NeoDove portal that triggers an **HTTP POST request** to your inventory system’s **URL endpoint** whenever a new order is placed. The inventory system **receives** the order details and **adjusts** the stock levels accordingly.

### Benefits:

***

* **Real-time Data Transfer:** Immediate notification and data transfer as events occur.
* **Efficiency:** Reduces the need for constant polling or checking for updates, saving bandwidth and resources.
* **Automation:** Enables automatic and seamless workflows between NeoDove and different applications and services.

### Steps:

***

1. **Log in** to your NeoDove account (<https://connect.neodove.com/login>)  &#x20;
2. &#x20;Go to the **Integrations** section, present on the left side-bar of your **screen**.

<figure><img src="/files/lxQOI9FGkynf6RR06dzk" alt=""><figcaption></figcaption></figure>

1. Once clicked, then need to click on the "**Webhook**" option.

<figure><img src="/files/ydAaUAyMYvz1h9t9Gzrs" alt=""><figcaption></figcaption></figure>

4. Post that, a new window will **appear** where you need to select the **events** on which the lead should behave or get triggered to some other software from NeoDove.

* **Trigger - 1 - Lead Create** (If you want the lead to be created in other software when it is being created in NeoDove)
* **Trigger - 2 - Lead Dispose** (If you want the lead to be created in other software when it is being disposed in NeoDove)
* **Trigger - 3 - Lead Delete** (If you want the lead to be created in other software when it is being deleted in NeoDove)

<figure><img src="/files/l5igsSOATc3lT75fpl7e" alt=""><figcaption></figcaption></figure>

5. After selecting the **triggering events**, need to put the "**Webhook URL**" for the software where you want the lead to be **created**.&#x20;

<figure><img src="/files/uE27PsiynFUTW9OQqUQE" alt=""><figcaption></figcaption></figure>

6. Then you need to click on the "**Save**" button to get the Webhook added and ensure to "**Turn it On**" as well for the webhook to work properly.

<figure><img src="/files/ygx9j39vVoUdrXrVw4vq" alt=""><figcaption></figcaption></figure>

7. After the webhook **gets added** successfully, you would be able to check the **lead event status** also for your analysis.

<figure><img src="/files/Rom3yvatiylc1ULIK41p" alt=""><figcaption></figcaption></figure>

&#x20;


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.neodove.com/admin-portal/integrations/webhook.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.