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, enabling users to interact with various Bitrix24 resources such as CRM entities and Smart Process Automation (SPA) types. Specifically, for the SPA resource with the "Update SPA" operation, the node allows updating records within Bitrix24's Smart Process Automation system.
Typical use cases include automating updates to SPA records based on external triggers or workflows, synchronizing data between Bitrix24 and other systems, or managing SPA entries programmatically without manual intervention.
For example, a user might update a SPA record's fields when a related event occurs in another application, ensuring that Bitrix24's SPA data stays current automatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication |
Note: The provided properties JSON only includes the "Authentication" property. The node supports additional properties like "Resource" and "Operation" internally, but these are not detailed here.
Output
The node outputs an array of items where each item contains a json object representing the response from Bitrix24 after processing the requested operation.
- For the "Update SPA" operation, the output JSON typically contains the updated SPA record details or confirmation of the update.
- If an error occurs and the node is configured to continue on failure, the output JSON will contain an
errorfield with the error message, along with theresourcename and a timestamp. - The node does not explicitly output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication token
- Webhook URL
- API key credential
- Uses Bitrix24 REST API endpoints to perform operations.
- The node relies on internal helper functions to make standardized API calls to Bitrix24.
- No additional external services beyond Bitrix24 are required.
Troubleshooting
Common Issues:
- Authentication failures due to incorrect or expired credentials.
- API rate limits or permission issues on the Bitrix24 side.
- Incorrect or missing parameters for the SPA update operation.
- Network connectivity problems.
Error Messages:
- Errors thrown during execution will include the error message returned by Bitrix24 or generated internally.
- If "Continue On Fail" is enabled, errors are returned in the output JSON under the
errorfield.
Resolutions:
- Verify that the selected authentication method is correctly configured and valid.
- Ensure the user has sufficient permissions in Bitrix24 to update SPA records.
- Check that all required input fields for the SPA update are provided and correctly formatted.
- Review Bitrix24 API documentation for any changes or limitations.
- Enable detailed logging to capture API responses for debugging.