> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/analyze/integrated-webhooks/integrated-webhooks-common-questions/integrated-webhooks-shopify-for-sprinthub.md).

# Integrated Webhooks - Shopify to SprintHub

## Adding Webhook Event in Shopify

To create a new Webhook in the Shopify dashboard, follow the steps below:

1. Access **Settings > Notifications**.
2. Click the **Webhooks** section and click **Create Webhook**.
3. On the creation screen, select the **event** that will be responsible for triggering the data to SprintHub.
4. Provide the **Passive Webhook URL**, which will be responsible for handling this data. For example, creating a lead or executing additional actions on an existing lead in the instance.

In this example, we will use the **Customer Creation**.

<figure><img src="/files/8a42e21de8c8569479dbd016aa5f113aec12674a" alt=""><figcaption><p><em>Shopify Notifications.</em></p></figcaption></figure>

<figure><img src="/files/892c07139acca799f754b29d2eb31732a5819dcf" alt=""><figcaption><p><em>Shopify Webhooks</em>.</p></figcaption></figure>

<figure><img src="/files/e8874a2ee24424e4f1b8f06d8f5c6d7f4ec78452" alt=""><figcaption><p><em>Add Webhook Modal.</em></p></figcaption></figure>

## Doing Automatic Event Mapping

To perform automatic mapping:

1. In SprintHub's Passive Webhook, click **Automatic Mapping**.
2. Then, go to Shopify and click **Send Test** within the Webhook configuration.\
   This will send a test trigger to SprintHub, allowing the platform to identify and map the fields automatically.

<figure><img src="/files/7540cd9717269ca4ad72e109cd33804f715a5a30" alt=""><figcaption><p><em>Sprinthub Webhook.</em></p></figcaption></figure>

<figure><img src="/files/3eb082c32e7dec27f6271b41f9072429ba2fe842" alt=""><figcaption><p><em>Send Test Button.</em></p></figcaption></figure>

## Webhook Settings

The **"Identifier for"** field defines which JSON key will be used as the lead's unique identifier — for example, the WhatsApp number — once the data arrives at SprintHub's Passive Webhook.\
If a lead with that identifier already exists in the database, it **will not be recreated**; only the **configured extra actions** will be executed.

<figure><img src="/files/18de445fc5d12d07099c50dfbd2ba954fbcd97a1" alt=""><figcaption><p><em>Identifier for.</em></p></figcaption></figure>

<figure><img src="/files/cb9058c9560f4af884f2c221565c90ae4c5b5677" alt=""><figcaption><p><em>Automatic Lead Creation.</em></p></figcaption></figure>

## Checking the Webhook Log

Inside the Webhook, it is possible to view the **log record**, including information such as created leads, identified leads, and other relevant details.\
It is important to highlight that all data sent by Shopify will be present in the **request body** (key `body`).\
There, it is possible to analyze each field sent in the event — such as **customer ZIP code**, **full name**, **email**, among others — making it easier to understand and map the data.

<figure><img src="/files/56239d5d19848be702259462dc50639f424b3b04" alt=""><figcaption><p><em>'Webhook Received' Record.</em></p></figcaption></figure>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.sprinthub.com/en/topics/analyze/integrated-webhooks/integrated-webhooks-common-questions/integrated-webhooks-shopify-for-sprinthub.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.