> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/ai-store/configure-webhooks-in-e-commerce-store.md).

# Configure Webhooks in E-Commerce Store

#### Step 1: Open Webhooks

1. Go to **Ecom Store** from the left-hand menu.
2. Scroll down and click on **Webhook**.
3. You will see the list of existing webhooks.
4. The list displays the **Status, Title, URL, Event,** and available **Actions**.

#### Step 2: Create a Webhook

1. Click **Create Webhook** from the top-right corner.
2. Enter the required webhook details.

#### Step 3: Add Webhook Title

1. Enter a descriptive **Title** for the webhook.
2. For example: `WhatsApp Order Webhook` or `CRM New Order Webhook`.
3. The title is only used to identify the webhook inside the Ecom Store.

#### Step 4: Add Webhook URL

1. Enter the **Webhook URL** where the event data should be sent.
2. You can use an endpoint from your **CRM, automation platform, backend,** or other external application.
3. If you are using a custom webhook from the panel:
   * Go to **Automation**.
   * Open **Custom Webhook**.
   * Copy the webhook URL.
   * Paste it into the Ecom Store webhook URL field.

#### Step 5: Select Event

1. Click **Select an Event**.
2. Choose the event that should trigger the webhook.
3. Depending on the available options, events may include:
   * WhatsApp Checkout
   * Abandoned Cart
   * Order Updated
   * Order Deleted
   * WhatsApp Payment
   * Cart Created or Updated
   * Customer Address Details
4. Select the required event.

#### Step 6: Set Webhook Status

1. Set the webhook **Status** to **Active** to enable it.
2. You can disable it temporarily when testing or when the integration is not required.

#### Step 7: Create the Webhook

1. Review the **Title, Webhook URL, Event,** and **Status**.
2. Click **Create Webhook**.
3. The webhook will be added to the webhook list.

#### Step 8: Monitor the Webhook

From the main webhook section, you can view:

* Webhook status
* Webhook title
* Configured URL
* Selected event
* Available actions

#### How Webhooks Work

Once the webhook is active, whenever the selected event occurs in your Ecom Store, the store automatically sends the relevant event data to the configured URL.

For example, if you configure a webhook for **Order Updated**, whenever an order is updated, the order information can automatically be sent to your CRM or automation platform.

{% embed url="<https://www.youtube.com/watch?v=O8jDHGm2FJg>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/ai-store/configure-webhooks-in-e-commerce-store.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.