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 Status" operation, the node fetches status or related information about Smart Process Automation entities within Bitrix24.
Common scenarios where this node is beneficial include:
- Automating workflows that depend on the current status of SPA entities.
- Monitoring SPA items programmatically to trigger further actions in n8n.
- Integrating Bitrix24 SPA data into other systems or dashboards.
For example, a user might use this node to retrieve the status of a specific SPA item and then update a record in another system based on that status.
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 JSON objects representing the response from Bitrix24 for the requested SPA status or related data. The exact structure depends on the Bitrix24 API response for the SPA resource and operation invoked.
If an error occurs and the node is configured to continue on failure, the output will contain an object with an error field describing the issue, along with the resource name and a timestamp.
No binary data output is indicated by the source code.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Uses internal helper functions to make standardized API calls to Bitrix24 endpoints.
- No additional external services beyond Bitrix24 are required.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or expired credentials.
- API rate limits or permission restrictions from Bitrix24.
- Network connectivity problems affecting API calls.
Error messages:
- Errors thrown during execution will include the message from the Bitrix24 API or internal errors.
- If "Continue On Fail" is enabled, errors are returned as part of the output JSON with fields
error,resource, andtimestamp.
Resolutions:
- Verify and refresh authentication credentials.
- Check Bitrix24 API permissions and scopes.
- Ensure network access to Bitrix24 endpoints.
- Enable "Continue On Fail" to handle errors gracefully in workflows.