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 "Set SPA Config" operation, it allows configuring or updating settings related to Smart Process Automation entities within Bitrix24.
Common scenarios where this node is beneficial include automating business workflows by programmatically managing SPA configurations, integrating SPA data into other systems, or customizing SPA behavior based on external triggers.
For example, a user might use this node to update SPA entity fields dynamically when certain conditions are met in their workflow, or to set up SPA configurations as part of a larger automation pipeline that involves CRM data synchronization.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Output
The node outputs an array of items, each containing a json object representing the response from Bitrix24 after processing the requested operation. The structure of the JSON depends on the specific SPA configuration changes made but generally includes details about the updated SPA entity or confirmation of the applied settings.
If an error occurs during execution and the node is configured to continue on failure, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
No binary data output is indicated in the source code.
Dependencies
- Requires authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- Relies on Bitrix24's REST API endpoints to fetch and manipulate SPA and CRM data.
- Uses internal helper functions (
makeStandardBitrix24Call) to perform API calls. - No additional external services beyond Bitrix24 are required.
Troubleshooting
Common Issues:
- Authentication failures due to incorrect or expired credentials.
- API rate limits or permission errors from Bitrix24.
- Missing or invalid SPA type identifiers when setting configurations.
- Network connectivity issues affecting API calls.
Error Messages:
- Errors returned from Bitrix24 API calls will be propagated and may appear in the output if "continue on fail" is enabled.
- Messages like "Failed to load SPA fields" or "Failed to load SPA types" indicate problems fetching necessary metadata; ensure correct permissions and valid parameters.
Resolutions:
- Verify and refresh authentication credentials.
- Check Bitrix24 user permissions for accessing SPA configurations.
- Confirm that SPA type IDs and other parameters are correctly specified.
- Ensure stable network connection and retry if transient errors occur.