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 node integrates with Bitrix24's Smart Process Automation (SPA) feature, specifically enabling the update of SPA items. It allows users to modify fields of an existing SPA item by specifying the item ID and the type of SPA entity. This is useful in scenarios where automated workflows or CRM processes require updating records dynamically based on external triggers or data changes.
For example, a user might want to update a customer support ticket's status or priority in Bitrix24 SPA when a related event occurs in another system, such as a new email or form submission.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2, Webhook URL, or API Key |
| Type ID | The identifier of the Smart Process type to which the item belongs |
| Item ID | The unique identifier of the SPA item to update |
| Fields | Collection of fields to update on the SPA item. Each field includes: - Field Name: select from available fields for the chosen SPA type - Field Value: value to set for the field |
| Use JSON Format for Fields | Whether to provide the fields as a JSON object instead of individual field entries |
| Fields (JSON) | JSON object representing fields and their values to update (used if "Use JSON Format for Fields" is true) |
Output
The node outputs an array of items, each containing a json property with the response from Bitrix24 after attempting to update the SPA item. The structure typically includes confirmation of the update or details about the updated item.
If an error occurs and the node is configured to continue on failure, the output will include an error field with the error message, the resource name, and a timestamp.
No binary data output is produced by this node.
Dependencies
- Requires access to a Bitrix24 account with appropriate permissions to manage Smart Process Automation entities.
- Requires authentication credentials configured in n8n, supporting OAuth2, webhook URL, or API key methods.
- Relies on Bitrix24 API endpoints for SPA types, fields, and item updates.
- Uses internal helper functions to make standardized API calls to Bitrix24.
Troubleshooting
Common Issues:
- Incorrect or missing SPA Type ID or Item ID can cause failures in locating the item to update.
- Providing invalid field names or values not matching the expected format may result in API errors.
- Authentication misconfiguration can lead to authorization errors.
Error Messages:
- Errors returned from Bitrix24 API are surfaced in the node output under the
errorfield if "Continue On Fail" is enabled. - Common messages include "Failed to load SPA types," "Failed to load SPA fields," or specific API error messages indicating invalid parameters or permission issues.
- Errors returned from Bitrix24 API are surfaced in the node output under the
Resolutions:
- Verify that the SPA Type ID corresponds to an existing Smart Process type in Bitrix24.
- Ensure the Item ID exists and is accessible with the provided credentials.
- Double-check field names against those loaded dynamically for the selected SPA type.
- Confirm authentication credentials are valid and have sufficient permissions.