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 workflows. Specifically, for the Workflow resource with the Kill Workflow operation, it enables terminating or stopping a running workflow within Bitrix24.
Common scenarios where this node is beneficial include:
- Automating business processes by programmatically stopping workflows that are no longer needed.
- Managing workflow executions dynamically based on external triggers or conditions.
- Integrating Bitrix24 workflow control into larger automation pipelines.
For example, if a certain condition in your sales process changes (like a deal being lost), you might want to kill an associated workflow to prevent further actions.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Output
The node outputs JSON data representing the result of the requested operation on the Bitrix24 platform. For the Kill Workflow operation, the output typically includes confirmation of the workflow termination or error details if the operation failed.
If the node encounters an error and "Continue On Fail" is enabled, it outputs an object containing:
error: The error message.resource: The resource name ("workflow" in this context).timestamp: The ISO timestamp when the error occurred.
No binary data output is indicated in the source code.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Uses internal helper functions to make API calls to Bitrix24.
- No additional external services beyond Bitrix24 itself are required.
- Proper configuration of authentication credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials can cause failures.
- Insufficient permissions in Bitrix24 to kill workflows.
- Network connectivity problems preventing API calls.
- Incorrect resource or operation parameters.
Error messages:
- Errors returned from Bitrix24 API will be propagated and can be seen in the output JSON under the
errorfield if "Continue On Fail" is enabled. - If the node throws an exception, ensure credentials and parameters are correct.
- Errors returned from Bitrix24 API will be propagated and can be seen in the output JSON under the
Resolution tips:
- Verify that the selected authentication method is correctly configured.
- Check Bitrix24 user permissions for workflow management.
- Enable "Continue On Fail" to handle errors gracefully in workflows.
- Review API limits or restrictions imposed by Bitrix24.