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
The Bitrix24 node integrates with the Bitrix24 CRM and business platform, enabling automation workflows to interact with various Bitrix24 resources. Specifically, for the SPA (Smart Process Automation) resource and the Get SPA Status operation, this node fetches the current status or details of a Smart Process entity within Bitrix24.
This node is beneficial in scenarios where users want to automate monitoring or processing of Smart Process records, such as tracking workflow progress, updating dashboards, or triggering subsequent actions based on SPA status changes.
Practical examples:
- Automatically retrieving the status of a custom Smart Process record after an update.
- Integrating SPA status checks into broader CRM automation workflows.
- Using SPA data to trigger notifications or escalate tasks when certain statuses are reached.
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 response from Bitrix24's API regarding the SPA status. The structure typically includes fields describing the SPA entity's current state, metadata, and any relevant attributes returned by the Bitrix24 API.
If the node supports binary data output (not explicitly shown in the provided code), it would represent attachments or files related to the SPA entity, but this is not indicated here.
Dependencies
Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication token
- Webhook URL
- API key credential
Uses Bitrix24 API endpoints internally to retrieve SPA information.
The node depends on internal helper modules (
FieldRegistry,ResourceHandlerFactory, andGenericFunctions) to handle API calls and resource-specific logic.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 if the connected Bitrix24 user lacks access rights.
- Missing or invalid SPA type or entity IDs leading to empty or error responses.
Error messages:
- Errors thrown during execution will include the message from the Bitrix24 API or internal processing errors.
- If "continue on fail" is enabled, errors are returned as part of the output JSON with an
errorfield containing the message, along with the resource name and timestamp.
Resolutions:
- Verify that the selected authentication method is correctly configured and valid.
- Ensure the Bitrix24 account has sufficient permissions to access SPA data.
- Confirm that the SPA entity ID or parameters used are correct and exist in Bitrix24.