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 platform, allowing users to perform various operations on Bitrix24 resources. Specifically, for the Product resource and the Delete Product Property operation, it enables deleting a product property by its ID.
Typical use cases include automating the management of product properties in Bitrix24, such as removing outdated or incorrect product attributes programmatically within an n8n workflow. For example, if a product property is no longer relevant or was created by mistake, this node can delete it automatically based on the provided property ID.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Property ID | The unique identifier of the product property to delete. This is a required string input. |
Output
The node outputs JSON data representing the result of the deletion operation. If successful, the output typically contains confirmation details from Bitrix24 about the deleted property. In case of failure, the output includes an error message with the reason for failure and a timestamp.
The output structure looks like:
{
"json": {
// Result of the delete operation or error details
},
"pairedItem": {
"item": 0
}
}
No binary data output is produced by this node.
Dependencies
Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication token
- Webhook URL
- API key credential
The node depends on Bitrix24's API endpoints to manage product properties.
Proper configuration of credentials in n8n is necessary to authenticate API requests.
Troubleshooting
Common Issues:
- Invalid or missing Property ID: Ensure the Property ID is correct and exists in Bitrix24.
- Authentication failures: Verify that the selected authentication method is correctly configured and valid.
- API permission errors: The authenticated user must have sufficient permissions to delete product properties.
Error Messages:
- Errors returned from Bitrix24 API will be included in the output JSON under the
errorfield. - If the node is set to continue on fail, errors are captured and passed downstream; otherwise, the workflow execution stops.
- Errors returned from Bitrix24 API will be included in the output JSON under the
Resolution Tips:
- Double-check the Property ID value.
- Confirm that the API credentials are active and have the necessary scopes/permissions.
- Review Bitrix24 API limits or restrictions that might block deletion.
Links and References
This summary is based on static analysis of the node's source code and provided property definitions without runtime execution.