> 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-how-to-use-a-unique-id-so-there-are-no-lead-duplicates.md).

# Integrated Webhooks - How to use a unique ID so there are no duplicate leads

<figure><img src="/files/78ae77229a8b5bef2cc8bcfea0c10689494b2ce2" alt=""><figcaption></figcaption></figure>

At SprintHub, we understand the importance of maintaining data integrity and consistency in your platform. One of the most effective ways to ensure this is through the use of identifiers in fields that can prevent such duplication when your leads come from the webhook.

&#x20;In this article, we will explore how you can implement and use a unique ID to prevent data duplication and improve the efficiency of your operations.

**What is a Unique ID?**

A unique ID, as the name suggests, is an exclusive identifier assigned to each record, in our case, a specific lead field. It serves as a kind of primary key that distinguishes a specific record from all others.

**How to Use a Unique ID in SprintHub**

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

**Request Body and Field Identification**

If you want to avoid creating a lead identical to one that already exists on the platform, create fields such as email, phone, or WhatsApp which are in a way "universal" and common between your external system and SprintHub:&#x20;

<table><thead><tr><th width="132">Key </th><th width="120">First name </th><th width="83">Type </th><th width="136">Required</th><th>Unique ID</th></tr></thead><tbody><tr><td>name</td><td>First name</td><td>Text</td><td>None</td><td>#NONE#</td></tr><tr><td>email</td><td>Email</td><td>Text</td><td>Required</td><td>(Lead) Email</td></tr><tr><td>phone</td><td>Phone</td><td>Text</td><td>Required</td><td>(Lead) Mobile Phone</td></tr><tr><td>whatsapp</td><td>WhatsApp</td><td>Text</td><td>None</td><td>(Lead) WhatsApp</td></tr></tbody></table>

When performing the mapping in SprintHub, it is recommended to include a field for the unique ID of each record. This ID will serve as a primary key so that there is no duplication of leads.


---

# 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-how-to-use-a-unique-id-so-there-are-no-lead-duplicates.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.