Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify Actions
Overview
This node integrates with the Bitrix24 CRM and business platform, allowing users to perform various operations on Bitrix24 resources. Specifically, for the Product resource with the Delete Product operation, it enables deleting a product by its ID from the Bitrix24 system.
Common scenarios where this node is beneficial include:
- Automating cleanup of obsolete or discontinued products in Bitrix24.
- Integrating product lifecycle management workflows where products are removed based on external triggers.
- Synchronizing product data between Bitrix24 and other systems by removing deleted products automatically.
Practical example:
- A workflow that listens for product deletion events in an external inventory system and uses this node to delete corresponding products in Bitrix24 to keep both systems in sync.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler but less secure), API Key authentication. |
| Product ID | The unique identifier of the product to delete. This is a required string input. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the product was successfully deleted or provide error information if the deletion failed.
If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs an object containing:
error: The error message.resource: The resource name ("product").timestamp: The ISO timestamp when the error occurred.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, webhook URL, or API key.
- Needs appropriate credentials configured in n8n for the chosen authentication method.
- Relies on Bitrix24's API endpoints to perform the delete operation on the product resource.
Troubleshooting
Common issues:
- Invalid or missing Product ID will cause the operation to fail.
- Incorrect or expired authentication credentials can lead to authorization errors.
- Network connectivity problems may prevent API calls from succeeding.
Error messages:
- Errors returned from Bitrix24 API will be surfaced as error messages in the node output.
- If "Continue On Fail" is not enabled, the node will throw errors stopping the workflow.
Resolutions:
- Verify the Product ID is correct and exists in Bitrix24.
- Ensure authentication credentials are valid and have sufficient permissions.
- Check network connectivity and Bitrix24 service status.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 CRM Products API
- n8n documentation on creating custom nodes