> 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 for Sprinthub ## Adding a Webhook Event in Shopify To create a new Webhook in the Shopify dashboard, follow the steps below: 1. Access **Settings > Notifications**. 2. Click on the section **Webhooks** and click on **Create Webhook**. 3. On the creation screen, select the **event** that will be responsible for sending the data to SprintHub. 4. Enter the **Passive Webhook URL**, which will be responsible for handling this data. For example, creating a lead or performing additional actions on an existing lead in the instance. In this example, we will use the event **Customer Creation**.

## Performing Automatic Event Mapping To perform automatic mapping: 1. In SprintHub's Passive Webhook, click on **Automatic Mapping**. 2. Then, access Shopify and click on **Send Test** within the Webhook settings.\ This will send a test trigger to SprintHub, allowing the platform to identify and map the fields automatically.

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

## Checking the Webhook Record 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 note 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.