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
The Bitrix24 node allows interaction with the Bitrix24 CRM and business platform, specifically supporting operations on various resources including Smart Process Automation (SPA) entities. The "Get Item" operation for the SPA resource retrieves a single Smart Process item by its ID. This is useful when you want to fetch detailed information about a specific SPA record within Bitrix24.
Common scenarios include:
- Retrieving details of a particular SPA item to use in further workflow steps.
- Fetching SPA data for reporting or integration purposes.
- Accessing SPA items dynamically based on user input or other triggers.
Example: You have a workflow that triggers when a new SPA item is created elsewhere, and you want to get the full details of that item to process or update it.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key |
| Type ID | The Smart Process type identifier. Selects which SPA type to work with (required). |
| Item ID | The unique identifier of the SPA item to retrieve (required). |
Output
The node outputs an array of items where each item's json property contains the retrieved SPA item data as returned by the Bitrix24 API. The structure corresponds to the fields defined in the selected SPA type, including standard and custom fields.
If the node encounters an error and "Continue On Fail" is enabled, it outputs an object with an error message, the resource name, and a timestamp.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, webhook URL, or API key.
- Uses Bitrix24 API endpoints to fetch SPA types and SPA item fields dynamically.
- Requires proper configuration of credentials in n8n for the chosen authentication method.
- Relies on internal helper functions to make standardized API calls to Bitrix24.
Troubleshooting
Common issues:
- Invalid or missing SPA Type ID or Item ID parameters will cause the API call to fail.
- Authentication failures due to incorrect or expired credentials.
- Network or API rate limiting errors from Bitrix24.
Error messages:
- Errors returned from Bitrix24 API are propagated; typical messages might indicate invalid IDs or permission issues.
- If fields fail to load, the node may show messages like "Failed to load SPA types" or "Failed to load SPA fields".
Resolutions:
- Verify that the SPA Type ID and Item ID are correct and exist in your Bitrix24 account.
- Ensure credentials are valid and have sufficient permissions.
- Enable "Continue On Fail" to handle errors gracefully in workflows.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 Smart Process Automation Overview
- n8n documentation on Bitrix24 node (for general usage guidance)