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
The Bitrix24 node integrates with the Bitrix24 CRM and business platform, enabling automation workflows to interact with various Bitrix24 resources. Specifically, for the SPA (Smart Process Automation) resource and the Uninstall SPA operation, this node allows users to uninstall or remove a Smart Process Automation entity from their Bitrix24 environment.
This functionality is useful in scenarios where an organization needs to programmatically manage its Smart Processes, such as cleaning up unused automations, managing lifecycle of processes, or integrating process management into larger automated workflows.
Practical example:
- Automatically uninstall a specific Smart Process after it has completed or is no longer needed, triggered by an external event or schedule.
- Integrate Bitrix24 SPA management into a DevOps pipeline to maintain environment hygiene.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key |
Note: The provided input properties JSON only includes the "Authentication" property relevant to this operation. Other properties like SPA ID or parameters for uninstalling would be defined elsewhere in the full node configuration but are not explicitly shown here.
Output
The node outputs JSON data representing the result of the uninstall operation. The exact structure depends on the Bitrix24 API response but typically includes:
- Confirmation of successful uninstallation or error details.
- Metadata such as timestamps and resource identifiers.
If an error occurs and the node is configured to continue on failure, the output JSON will include an error field with the error message, the resource name, and a timestamp.
No binary data output is indicated for this operation.
Dependencies
Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication token
- Bitrix24 webhook URL
- Bitrix24 API key
Uses Bitrix24 REST API endpoints internally to perform operations.
The node relies on internal helper functions (
makeStandardBitrix24Call) to communicate with Bitrix24 APIs.Proper credentials must be configured in n8n for the chosen authentication method.
Troubleshooting
Common issues:
- Authentication failures due to invalid or expired tokens/keys.
- Insufficient permissions to uninstall SPA entities.
- Incorrect SPA type or ID specified leading to API errors.
- Network connectivity issues preventing API calls.
Error messages:
- Errors returned from Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical error messages might include authorization errors, "entity not found," or validation errors.
Resolutions:
- Verify that the correct authentication method and valid credentials are used.
- Ensure the user/account has sufficient rights to uninstall SPA entities.
- Double-check SPA IDs and parameters passed to the node.
- Check network connectivity and Bitrix24 service status.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 Smart Process Automation Overview
- n8n Documentation on Creating Custom Nodes
This summary is based solely on static analysis of the provided source code and input properties.