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 platform, allowing users to interact with various Bitrix24 resources such as CRM entities and business processes. Specifically, for the Status resource with the Delete Status operation, it enables deleting a status entry identified by its ID within Bitrix24.
Common scenarios where this node is beneficial include automating cleanup tasks in Bitrix24 workflows, managing lifecycle of statuses in CRM pipelines, or integrating status management into broader automation flows.
For example, you might use this node to automatically remove obsolete or deprecated statuses from your Bitrix24 CRM after certain conditions are met, ensuring your CRM data remains clean and relevant.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key |
| Status ID | The unique identifier of the status to delete. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
If an error occurs and the node is configured to continue on failure, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.
No binary data output is produced by this operation.
Dependencies
- Requires access to a Bitrix24 account.
- Requires authentication credentials configured in n8n:
- An OAuth2 token,
- Or a webhook URL,
- Or an API key credential.
- The node uses Bitrix24's REST API endpoints internally to perform operations.
Troubleshooting
Common Issues:
- Invalid or missing Status ID: Ensure the Status ID provided exists and is correct.
- Authentication failures: Verify that the selected authentication method is properly configured and valid.
- Insufficient permissions: The authenticated user must have rights to delete statuses in Bitrix24.
Error Messages:
- Errors returned from Bitrix24 API will be surfaced in the node output under the
errorfield if "Continue On Fail" is enabled. - Common errors include authorization errors, invalid parameters, or network issues.
- Errors returned from Bitrix24 API will be surfaced in the node output under the
Resolution Tips:
- Double-check the Status ID value.
- Confirm that the API credentials are current and have necessary scopes/permissions.
- Test connectivity to Bitrix24 API outside n8n to isolate network or permission problems.
Links and References
- Bitrix24 REST API Documentation
- Bitrix24 Official Website
- n8n documentation on Authentication and Bitrix24 Integration