> 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/lead-source/contact-book-integration.md).

# Contact Book Integration

#### Step 1: Create Connection

1. Go to **Lead Source**
2. Select **Contact Book**
3. Click **Create Connection**
4. Enter connection name
5. Click **Create Connection**

#### Step 2: Get Webhook & QR Code

1. Open the created connection
2. Go to **Configuration**
3. Copy **Webhook URL** (if required)
4. Note the **QR Code**

#### Step 3: Install Mobile App

1. Go to **Documentation**
2. Download the **Mobile App** using provided link
3. Install the app on your device

#### Step 4: Connect Mobile App

1. Open the mobile app
2. Click **Add Connection**
3. Select **Contact Book**
4. Scan the **QR Code** from panel

#### Step 5: Import Contacts

1. Select **Contact Source** (e.g., Device)
2. Click **Import & Sync Contacts**
3. Select contacts you want to import
4. Sync selected contacts

#### Step 6: Optional Settings

* Add **Webhook URL** for external integrations

#### Step 7: Monitor Logs

1. Go to **Logs Section**
2. Check contact data, sync status, and timestamps

* Integration is ready and importing contacts as leads 

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


---

# 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/lead-source/contact-book-integration.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.