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 interacts with the Bitrix24 platform, specifically focusing on Smart Process Automation (SPA) entities when using the "Get Types" operation. It retrieves a list of SPA types available in the Bitrix24 environment. This is useful for workflows that need to dynamically fetch and work with different SPA entity types, such as automating business processes, managing custom data structures, or integrating SPA data into other systems.
Practical examples include:
- Automatically listing all SPA types to populate dropdowns in subsequent workflow steps.
- Fetching SPA type IDs to query or manipulate specific SPA records.
- Integrating SPA metadata into reporting or synchronization tasks.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key. |
| Return All | Whether to return all results or limit the number of items returned. Applies to both "getTypes" and "getItems" operations. |
| Max pages to load | Maximum number of pages to load if not returning all results. Each page contains up to 50 items. Only relevant if "Return All" is false. |
| Options | Additional options to customize the request: - Filter: JSON object to filter results using Bitrix24 filter syntax. - Order: JSON object specifying sorting order. - Select: Comma-separated list of fields to return. |
Output
The output is an array of SPA type objects, each containing at least:
name: A string combining the SPA type title and its ID, e.g.,"Example Type (ID: 123)".value: The SPA type ID as a string.description: A textual description of the SPA type, typically the title or name.
The output is structured as JSON under the json property of each item. There is no binary data output for this operation.
Example output snippet:
[
{
"name": "Customer Feedback (ID: 101)",
"value": "101",
"description": "Customer Feedback"
},
{
"name": "Order Processing (ID: 102)",
"value": "102",
"description": "Order Processing"
}
]
Dependencies
- Requires connection to a Bitrix24 instance.
- Needs one of the supported authentication methods configured in n8n: OAuth2, Webhook URL, or API Key.
- Uses Bitrix24 API endpoints internally to fetch SPA types (
crm.type.list). - No additional external dependencies beyond standard Bitrix24 API access.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or expired credentials.
- API rate limits or pagination limits causing incomplete data retrieval.
- Network connectivity problems preventing API calls.
Error messages:
- Errors during SPA type loading will be logged and may appear as
"Failed to load SPA types: <error message>". - If no SPA types are found, the output may contain a placeholder entry indicating no types are available.
- Errors during SPA type loading will be logged and may appear as
Resolutions:
- Verify and refresh authentication credentials.
- Check network connectivity and Bitrix24 API availability.
- Adjust "Max pages to load" or enable "Return All" to ensure complete data retrieval.
- Review Bitrix24 API permissions for the authenticated user.