> For the complete documentation index, see [llms.txt](https://ledsak.gitbook.io/docs-for-ledsak/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ledsak.gitbook.io/docs-for-ledsak/integrations/cliniceo.md).
# Cliniceo
### **1. Overview**
Cliniceo is a powerful clinic management platform. When integrated with Ledsak CRM, it allows automatic syncing of patient data, payment completion status, and clinic information to enhance lead lifecycle tracking.
***
### **2. Accessing Cliniceo Integration Settings in Ledsak**
To begin the integration:
1. Log into your **Ledsak CRM** dashboard.
2. Navigate to **Integrations > Cliniceo**.
3. You will find fields to input your **Cliniceo credentials** and configure clinic-specific details.
***
### **3. Cliniceo Integration Fields**
#### **A. Account Name**
* Assign a unique name to this Cliniceo integration instance.
* This helps in identifying and managing multiple accounts if applicable.
#### **B. Cliniceo Name**
* Add a descriptive name that represents your Cliniceo account or clinic.
***
### **4. API Credentials**
To enable API communication between Ledsak and Cliniceo, provide the following credentials:
#### **A. API Key**
* **Location:** Log in to your Cliniceo account → Go to **Settings > API Access** → Copy the **API Key**.
#### **B. Business Key**
* **Location:** Available in Cliniceo’s API Access section alongside the API Key.
#### **C. API Secret**
* **Location:** Also located in the API Access section in Cliniceo.
> ⚠️ Ensure all keys are kept confidential. Do not share your keys publicly.
***
### **5. Adding Clinics**
Configure one or more clinics from Cliniceo by providing:
#### **A. Cliniceo Clinic ID**
* This ID uniquely identifies a clinic registered in your Cliniceo account.
* Retrieve this from the clinic settings inside Cliniceo.
#### **B. Select Clinic Branch**
* Choose the appropriate branch within Ledsak that corresponds to the Cliniceo clinic.
> 🔄 You can repeat this process to map multiple clinics.
***
### **6. Lead Conversion Mapping**
To ensure that lead progress is tracked effectively based on payment status:
#### **Select Lead Conversion Stage**
* Choose the stage in Ledsak CRM that should be automatically assigned **when a payment is marked as completed in Cliniceo**.
* Example: *“Converted”*, *“Client”*, or *“Payment Complete”*.
This setting ensures leads are automatically updated in Ledsak based on real activity in Cliniceo.
***
### **7. Activation**
#### **Is Activate?**
* Checkbox the switch to activate or deactivate the integration.
* If activated, data will start syncing between Cliniceo and Ledsak CRM based on your settings.
***
### **8. Related Documents**
You may refer to the following for more detailed API and workflow documentation:
* Ledsak.ai Help Center
***
### **9. Support**
If you encounter any issues during the integration:
* Contact **Ledsak Support** at:
---
# 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://ledsak.gitbook.io/docs-for-ledsak/integrations/cliniceo.md?ask=&goal=
```
`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.