{"id":9451675156754,"title":"Kommo Unlink Entities Integration","handle":"kommo-unlink-entities-integration","description":"\u003cbody\u003e```html\n\n\n\n \u003cmeta charset=\"UTF-8\"\u003e\n \u003cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"\u003e\n \u003ctitle\u003eUnderstanding Kommo API's Unlink Entities Endpoint\u003c\/title\u003e\n \u003cstyle\u003e\n body {\n font-family: Arial, sans-serif;\n }\n h1, h2 {\n color: #333;\n }\n p {\n font-size: 16px;\n line-height: 1.6;\n color: #666;\n }\n .section {\n margin-bottom: 20px;\n }\n \u003c\/style\u003e\n\n\n \u003cdiv class=\"content\"\u003e\n \u003ch1\u003eUnderstanding Kommo API's Unlink Entities Endpoint\u003c\/h1\u003e\n \u003cdiv class=\"section\"\u003e\n \u003ch2\u003eWhat Can Be Done with the Kommo API's Unlink Entities Endpoint\u003c\/h2\u003e\n \u003cp\u003eThe \u003cstrong\u003eKommo API's Unlink Entities\u003c\/strong\u003e endpoint is designed to manage relationships between different entities within the system. An 'entity' here refers to any object within Kommo, such as deals, contacts, companies, etc. The unlinking process allows for the removal of associations between these entities, effectively organizing and maintaining the integrity of data relationships within your CRM.\u003c\/p\u003e\n \u003c\/div\u003e\n \u003cdiv class=\"section\"\u003e\n \u003ch2\u003eProblems That Can Be Solved Using this Endpoint\u003c\/h2\u003e\n \u003cul\u003e\n \u003cli\u003e\n \u003cstrong\u003eClean up Data:\u003c\/strong\u003e Over time, the relations between entities can become outdated or incorrect. By unlinking irrelevant associations, you can keep your data clean and accurate.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eRecord Management:\u003c\/strong\u003e When a relationship between two records no longer exists or was established by mistake, it can be dissolved without affecting the entities directly.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eData Segregation:\u003c\/strong\u003e In instances where you need to separate data due to a change in business structures, policies, or in the preparation for data analysis, being able to unlink entities is crucial for successful segmentation.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eUser Access Control:\u003c\/strong\u003e When you need to restrict the visibility of certain relationships for privacy or security reasons, unlinking these allows you to maintain control over which users can see or interact with specific entity relationships.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eWorkflow Updates:\u003c\/strong\u003e Your business processes and workflows may change over time, necessitating updates to the relationships between records. Unlinking old relationships is an essential step in this update process.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eSystem Integrations:\u003c\/strong\u003e When integrating with other systems or migrating data, it's often necessary to redefine relationships. The unlinking process allows for correcting relationships in the system without creating duplicates.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eReduction of System Clutter:\u003c\/strong\u003e Redundant or excessive linkages in a CRM can lead to performance issues and complicate user operations. By unlinking unnecessary entities, system performance and usability can be improved.\n \u003c\/li\u003e\n \u003c\/ul\u003e\n \u003c\/div\u003e\n \u003c\/div\u003e\n\n\n```\n\nThe above HTML is a simple web page that explains the functionality and utility of the Kommo API's Unlink Entities endpoint. It uses HTML5 semantic elements, a standard UTF-8 charset, responsive meta tags, and includes internal CSS for basic styling.\n\nThe main content is organized into two main sections with headings to provide a clear structure for the web page. Each section has descriptive paragraphs and a list to outline the various problems and scenarios where the Unlink Entities endpoint can be useful. This format provides a comprehensive yet easy-to-understand overview of the Kommo API feature and its applications for maintaining data relationships within a CRM system.\u003c\/body\u003e","published_at":"2024-05-13T11:30:27-05:00","created_at":"2024-05-13T11:30:28-05:00","vendor":"Kommo","type":"Integration","tags":[],"price":0,"price_min":0,"price_max":0,"available":true,"price_varies":false,"compare_at_price":null,"compare_at_price_min":0,"compare_at_price_max":0,"compare_at_price_varies":false,"variants":[{"id":49119115706642,"title":"Default Title","option1":"Default Title","option2":null,"option3":null,"sku":"","requires_shipping":true,"taxable":true,"featured_image":null,"available":true,"name":"Kommo Unlink Entities Integration","public_title":null,"options":["Default Title"],"price":0,"weight":0,"compare_at_price":null,"inventory_management":null,"barcode":null,"requires_selling_plan":false,"selling_plan_allocations":[]}],"images":["\/\/consultantsinabox.com\/cdn\/shop\/files\/28bd282e5aea2f3950af5aa1745ec36b_1e0b1632-9a36-4ed2-9806-fce47e8f2c6b.png?v=1715617828"],"featured_image":"\/\/consultantsinabox.com\/cdn\/shop\/files\/28bd282e5aea2f3950af5aa1745ec36b_1e0b1632-9a36-4ed2-9806-fce47e8f2c6b.png?v=1715617828","options":["Title"],"media":[{"alt":"Kommo Logo","id":39142729515282,"position":1,"preview_image":{"aspect_ratio":1.0,"height":512,"width":512,"src":"\/\/consultantsinabox.com\/cdn\/shop\/files\/28bd282e5aea2f3950af5aa1745ec36b_1e0b1632-9a36-4ed2-9806-fce47e8f2c6b.png?v=1715617828"},"aspect_ratio":1.0,"height":512,"media_type":"image","src":"\/\/consultantsinabox.com\/cdn\/shop\/files\/28bd282e5aea2f3950af5aa1745ec36b_1e0b1632-9a36-4ed2-9806-fce47e8f2c6b.png?v=1715617828","width":512}],"requires_selling_plan":false,"selling_plan_groups":[],"content":"\u003cbody\u003e```html\n\n\n\n \u003cmeta charset=\"UTF-8\"\u003e\n \u003cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"\u003e\n \u003ctitle\u003eUnderstanding Kommo API's Unlink Entities Endpoint\u003c\/title\u003e\n \u003cstyle\u003e\n body {\n font-family: Arial, sans-serif;\n }\n h1, h2 {\n color: #333;\n }\n p {\n font-size: 16px;\n line-height: 1.6;\n color: #666;\n }\n .section {\n margin-bottom: 20px;\n }\n \u003c\/style\u003e\n\n\n \u003cdiv class=\"content\"\u003e\n \u003ch1\u003eUnderstanding Kommo API's Unlink Entities Endpoint\u003c\/h1\u003e\n \u003cdiv class=\"section\"\u003e\n \u003ch2\u003eWhat Can Be Done with the Kommo API's Unlink Entities Endpoint\u003c\/h2\u003e\n \u003cp\u003eThe \u003cstrong\u003eKommo API's Unlink Entities\u003c\/strong\u003e endpoint is designed to manage relationships between different entities within the system. An 'entity' here refers to any object within Kommo, such as deals, contacts, companies, etc. The unlinking process allows for the removal of associations between these entities, effectively organizing and maintaining the integrity of data relationships within your CRM.\u003c\/p\u003e\n \u003c\/div\u003e\n \u003cdiv class=\"section\"\u003e\n \u003ch2\u003eProblems That Can Be Solved Using this Endpoint\u003c\/h2\u003e\n \u003cul\u003e\n \u003cli\u003e\n \u003cstrong\u003eClean up Data:\u003c\/strong\u003e Over time, the relations between entities can become outdated or incorrect. By unlinking irrelevant associations, you can keep your data clean and accurate.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eRecord Management:\u003c\/strong\u003e When a relationship between two records no longer exists or was established by mistake, it can be dissolved without affecting the entities directly.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eData Segregation:\u003c\/strong\u003e In instances where you need to separate data due to a change in business structures, policies, or in the preparation for data analysis, being able to unlink entities is crucial for successful segmentation.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eUser Access Control:\u003c\/strong\u003e When you need to restrict the visibility of certain relationships for privacy or security reasons, unlinking these allows you to maintain control over which users can see or interact with specific entity relationships.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eWorkflow Updates:\u003c\/strong\u003e Your business processes and workflows may change over time, necessitating updates to the relationships between records. Unlinking old relationships is an essential step in this update process.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eSystem Integrations:\u003c\/strong\u003e When integrating with other systems or migrating data, it's often necessary to redefine relationships. The unlinking process allows for correcting relationships in the system without creating duplicates.\n \u003c\/li\u003e\n \u003cli\u003e\n \u003cstrong\u003eReduction of System Clutter:\u003c\/strong\u003e Redundant or excessive linkages in a CRM can lead to performance issues and complicate user operations. By unlinking unnecessary entities, system performance and usability can be improved.\n \u003c\/li\u003e\n \u003c\/ul\u003e\n \u003c\/div\u003e\n \u003c\/div\u003e\n\n\n```\n\nThe above HTML is a simple web page that explains the functionality and utility of the Kommo API's Unlink Entities endpoint. It uses HTML5 semantic elements, a standard UTF-8 charset, responsive meta tags, and includes internal CSS for basic styling.\n\nThe main content is organized into two main sections with headings to provide a clear structure for the web page. Each section has descriptive paragraphs and a list to outline the various problems and scenarios where the Unlink Entities endpoint can be useful. This format provides a comprehensive yet easy-to-understand overview of the Kommo API feature and its applications for maintaining data relationships within a CRM system.\u003c\/body\u003e"}