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 including CRM entities and Smart Process Automation (SPA) types. Specifically, for the SPA resource with the "Get SPA Config" operation, the node fetches configuration details related to Smart Process Automation types within Bitrix24.
Common scenarios where this node is beneficial include:
- Automating workflows that require retrieving SPA type configurations.
- Integrating Bitrix24 SPA data into other systems or processes.
- Dynamically loading SPA fields and types for further processing or decision-making in automation.
For example, a user might use this node to get the list of available SPA types and their fields to build custom forms or automate data entry based on SPA configurations.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication |
Output
The node outputs an array of items where each item contains a json object representing the response from Bitrix24 API calls related to the selected resource and operation.
For the "Get SPA Config" operation under the SPA resource, the output JSON typically includes:
- Details about SPA types, such as their IDs, titles, and descriptions.
- Configuration fields associated with SPA types.
- Metadata like timestamps and error messages if applicable.
If the node encounters an error and "Continue On Fail" is enabled, it outputs an item with an error field describing the issue, along with the resource name and a timestamp.
The node does not explicitly output binary data.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Uses Bitrix24 REST API endpoints internally to fetch SPA-related data.
- No additional external services are required beyond Bitrix24 itself.
- The node depends on internal helper functions to make standardized API calls to Bitrix24.
Troubleshooting
Common Issues:
- Authentication failures due to incorrect or expired credentials.
- API rate limits or permission restrictions on the Bitrix24 account.
- Network connectivity issues preventing access to Bitrix24 APIs.
- Missing or invalid SPA type identifiers when fetching specific configurations.
Error Messages:
- Errors returned from Bitrix24 API calls will be included in the output if "Continue On Fail" is enabled.
- Messages like "Failed to load SPA types" or "No SPA types available" indicate problems retrieving SPA data, possibly due to permissions or empty configurations.
- If the node throws errors related to missing parameters (e.g., entityTypeId), ensure all required inputs are provided.
Resolutions:
- Verify and update authentication credentials.
- Check Bitrix24 user permissions for accessing SPA configurations.
- Ensure network connectivity and API endpoint accessibility.
- Provide all necessary input parameters, especially SPA type identifiers.