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 Settings" operation under the "SPA" resource allows users to retrieve configuration and metadata related to Smart Process Automation (SPA) types within Bitrix24.
Typical use cases include:
- Fetching SPA type definitions and settings to dynamically configure workflows.
- Automating processes based on SPA metadata.
- Integrating SPA data into other systems or reporting tools.
For example, a user might use this node to get all available SPA types and their fields to build a custom form or automate data entry in Bitrix24.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key |
The node also requires selecting the Resource ("SPA" in this case) and the Operation ("Get SPA Settings"). Additional parameters may be dynamically loaded depending on the SPA type selected, but these are not explicitly listed here.
Output
The node outputs JSON data representing the results of the requested SPA settings or metadata. This typically includes:
- Lists of SPA types with their IDs and titles.
- Detailed field information for a given SPA type, including field names, types, and whether they are required or read-only.
- Other SPA-related configuration data such as automation enablement status.
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.
The node does not output binary data.
Dependencies
- Requires a valid Bitrix24 authentication credential configured in n8n. Supported authentication methods are OAuth2, webhook URL, or API key.
- Uses Bitrix24 REST API endpoints such as
crm.type.listandcrm.item.fieldsto fetch SPA types and fields. - Relies on internal helper functions to make standardized API calls to Bitrix24.
Troubleshooting
Common issues:
- Authentication failures due to invalid or expired credentials.
- API rate limits or connectivity issues with Bitrix24.
- Missing or incorrect SPA type ID parameter causing empty or error responses.
Error messages:
- Errors returned from Bitrix24 API calls will appear in the output's
errorfield. - If the node fails to load SPA types or fields, it returns descriptive error messages like "Failed to load SPA types" or "Failed to load SPA fields".
- Errors returned from Bitrix24 API calls will appear in the output's
Resolutions:
- Verify that the chosen authentication method is correctly set up and authorized.
- Ensure the SPA type ID parameter is provided when required.
- Check network connectivity and Bitrix24 API status.
- Enable "Continue On Fail" option if you want the workflow to proceed despite errors.