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, specifically enabling interaction with its CRM and business automation features. The "Get SPA Info" operation under the "SPA" resource allows users to retrieve detailed information about Smart Process Automation (SPA) entities within Bitrix24.
Typical use cases include:
- Fetching metadata or configuration details of SPA types for automation workflows.
- Integrating SPA data into external systems or dashboards.
- Automating processes based on SPA entity information.
For example, a user might want to get all available SPA types and their fields to dynamically build forms or reports in an external application.
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 JSON data representing the result of the requested SPA information retrieval. The structure depends on the specific SPA info requested but generally includes:
- Details about SPA types such as IDs, titles, and descriptions.
- Field definitions for SPA entities including field names, types, and whether they are required or read-only.
- Metadata related to SPA automation capabilities.
If an error occurs during execution, the output JSON will contain an error field with the error message, the resource name, and a timestamp.
The node does not explicitly output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Uses Bitrix24 REST API endpoints such as
crm.type.listandcrm.item.fieldsto fetch SPA-related data. - Relies on internal helper functions to make authenticated API calls to Bitrix24.
No additional external services or environment variables beyond the configured Bitrix24 credentials are needed.
Troubleshooting
Common Issues:
- Authentication failures due to incorrect or expired credentials.
- API rate limits or permission restrictions from Bitrix24.
- Missing or invalid SPA type identifiers when requesting fields.
Error Messages:
- Errors returned from Bitrix24 API calls will be surfaced in the output JSON's
errorfield. - If the node fails to load SPA types or fields, it returns descriptive error messages indicating the failure reason.
- Errors returned from Bitrix24 API calls will be surfaced in the output JSON's
Resolutions:
- Verify that the selected authentication method is correctly configured and has sufficient permissions.
- Ensure the SPA type ID parameter is provided and valid when fetching SPA item fields.
- Check Bitrix24 API quotas and adjust usage accordingly.