Actions31
- 袙芯褉芯薪泻邪 锌褉芯写邪卸 Actions
- 小褌邪褌褍褋 胁芯褉芯薪泻懈 Actions
- 小屑邪褉褌-锌褉芯褑械褋褋 Actions
- 袩芯写褉邪蟹写械谢械薪懈械 Actions
- 小褌邪褌懈褋褌懈泻邪 蟹胁芯薪泻芯胁 Actions
- 袟邪写邪褔邪 Actions
- 孝芯胁邪褉薪邪褟 锌芯蟹懈褑懈褟 Actions
袙芯褉芯薪泻邪 锌褉芯写邪卸 → Delete
AI-generatedOverview
This node performs delete operations on various Bitrix24 auxiliary resources, specifically including categories, statuses, departments, tasks, product rows, and smart process types. It is useful for automating the removal of these entities within Bitrix24 CRM, such as deleting a category, status, or task by their ID. This helps maintain and manage CRM data efficiently by programmatically removing obsolete or unwanted records.
Use Case Examples
- Delete a category by its ID to clean up unused categories in the CRM.
- Remove a specific status from a deal stage to update the sales process.
- Delete a department to reflect organizational changes.
- Delete a task that is no longer relevant or was created in error.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the resource item to delete. Required for delete operations on categories, statuses, departments, tasks, product rows, and smart process types. |
Output
JSON
success- Indicates if the delete operation was successful (true) or not.id- The ID of the deleted resource item.
Dependencies
- Bitrix24 API authentication via an API key credential
Troubleshooting
- Common issues include providing an invalid or non-existent ID, which will cause the API to fail the delete operation.
- If the node throws a Bitrix24 API error, verify that the API credentials are correct and have sufficient permissions to delete the specified resource.
- Ensure the resource and operation parameters are correctly set to 'category' and 'delete' (or other resource types) and 'delete' respectively, as mismatches can cause unexpected errors.