> For the complete documentation index, see [llms.txt](https://daton-sarasanalytics.gitbook.io/daton/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daton-sarasanalytics.gitbook.io/daton/integrations/data-sources/saas-integrations/zohodesk.md). # ZohoDesk ZohoDesk ETL connector for data replication ### Snapshot | Features | Details | | ------------------------------- | ---------------- | | Release Status | Released | | Source API Version | v1 | | Table Selection | Yes | | Column Selection | Yes | | Edit Integration | Yes | | Replication Type Selection | No | | Authentication Parameters | OAuth | | Replication Type | Full Replication | | Replication Key | Date | | Suggested Replication Frequency | 24 hrs | | Tables/APIs Supported | | | --------------------- | -------- | | Agents | Profiles | | Roles | Teams | | Departments | Tickets | | Tasks | Products | | Contacts | Accounts | ### Integrate ZohoDesk with Daton 1. Signin to Daton 2. Select ZohoDesk from Integrations page 3. Provide Integration Name, Replication Frequency, and History. Integration name would be used in creating tables for the integration and cannot be changed later 4. Provide ZohoDesk with the necessary permissions on the OAuth pop-up window by selecting "Okay". 5. Post successful authentication, you will be prompted to choose from the list of available tables 6. Then select all required fields for each table 7. Submit the integration ### Workflow 1. Integrations would be in Pending state initially and will be moved to Active state as soon as the first job loads data successfully on to the configured warehouse 2. Users would be able to edit/pause/re-activate/delete integration anytime 3. Users can view job status and process logs from the integration details page by clicking on the integration name from the active list ### ZohoDesk Data **Agents** Purpose: Gives the list of all “full-time” and “occasional” agents in organization. Source API Documentation Replication: Full Replication Replication Key: NA **Fields** **Profiles** Purpose: Gives the list of profiles in organization. Source API Documentation Replication: Full Replication Replication Key: NA **Fields** **Roles** Purpose: Gives the list of all different Roles present in organization. Source API Documentation Replication: Full Replication Replication Key: NA **Fields** **Teams** Purpose: Gives the list of all teams in organization. Source API Documentation Replication: Full Replication Replication Key: NA **Fields** **Departments** Purpose: Gives the list of all departments in organization. Source API Documentation Replication: Full Replication Replication Key: NA **Fields** **Tickets** Purpose: Gives the list of all tickets in organization. Source API Documentation Replication: Full Replication Replication Key: NA **Fields** **Tasks** Purpose: Gives the list of all tasks in organization. Source API Documentation Replication: Full Replication Replication Key: NA **Fields** **Products** Purpose: Gives the list of all products from your helpdesk Source API Documentation Replication: Full Replication Replication Key: NA **Fields** --- # 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://daton-sarasanalytics.gitbook.io/daton/integrations/data-sources/saas-integrations/zohodesk.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.