> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/crm/integrating-with-leadsquared.md).
# Integrating with LeadSquared
Connect LeadSquared to Drivetrain and sync CRM and marketing data into revenue planning. Covers creating a dedicated Drivetrain admin user.
[Prerequisites](#prerequisites)
[LeadSquared Setup](#leadsquared-setup)\
[Step 1: Creating a New User](#step-1-creating-a-new-user)
## Prerequisites
To connect LeadSquared to Drivetrain, you need:
* An active LeadSquared account
* Admin privileges on LeadSquared
* Admin privileges in Drivetrain
## LeadSquared Setup
Drivetrain supports integration with LeadSquared via API from a **dedicated user account**. To get started you would need to create a dedicated profile and a dedicated user with administrator privileges on LeadSquared for Drivetrain.
### Step 1: Creating a New User
1. Access the LeadSquared Platform.
2. Navigate to the profile icon and click **Manage Users**.
3. At the top right, click on **Create.**
4. Create a new user with the name ***Drivetrain Integration.*** The email address will be provided to you by your Drivetrain Customer Success Manager.
5. Under **Role,** select ***Administrator*** and under **User Type** select ***Regular.***
6. \[Optional] You can select a reporting manager and Team appropriately.
7. Click on **Create New.**
{% hint style="info" %}
That’s it! Inform your customer success manager so that they can get started!
{% endhint %}
---
# 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://integrations.drivetrain.ai/integration-guide/readme/crm/integrating-with-leadsquared.md?ask=&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.
