Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
This node integrates with the Bitrix24 platform, specifically enabling interaction with its Smart Process Automation (SPA) features. The "Get SPA Config" operation retrieves configuration details related to SPA types within a Bitrix24 account. This is useful for users who want to dynamically fetch and work with SPA metadata, such as available SPA types and their fields, to automate business processes or customize CRM workflows.
Practical examples include:
- Automatically loading SPA type configurations to build dynamic forms or interfaces.
- Fetching SPA field definitions to map data between Bitrix24 and other systems.
- Using SPA metadata to trigger conditional automation based on SPA type properties.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key |
Output
The node outputs JSON data representing the SPA configuration retrieved from Bitrix24. The structure depends on the specific SPA config requested but generally includes:
- Details about SPA types, such as IDs, titles/names, and entity type identifiers.
- Field definitions for SPA items, including field names, types, whether they are required or read-only.
- Metadata about SPA automation capabilities and categories.
If an error occurs during execution, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.
No binary data output is produced by this node.
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 beyond Bitrix24 are required.
- The node relies 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 in Bitrix24 preventing access to SPA data.
- Missing or invalid SPA type identifiers when attempting to load fields.
Error Messages:
- Errors returned from Bitrix24 API calls will be surfaced in the output's
errorfield. - If the node cannot load SPA types or fields, it returns descriptive messages like "Failed to load SPA types" or "No fields found for this SPA type".
- Errors returned from Bitrix24 API calls will be surfaced in the output's
Resolutions:
- Verify that the selected authentication method is correctly configured and has sufficient permissions.
- Ensure the Bitrix24 user or API key has access to the SPA modules.
- Confirm that SPA types exist in the Bitrix24 account before requesting their configuration.