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 Bitrix24's Smart Process Automation (SPA) feature to create new SPA items. It allows users to specify the SPA type and set field values for the new item, either through individual fields or a JSON object. This is useful in automating business workflows where custom data structures are managed within Bitrix24, such as creating records for custom processes like project tracking, inventory management, or any tailored CRM extensions.
Practical examples include:
- Automatically creating a new SPA record when a form is submitted on a website.
- Generating SPA items based on events from other systems via webhook triggers.
- Populating SPA items with data from other Bitrix24 modules or external APIs.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2, Webhook URL, or API Key. |
| Type ID | The identifier of the Smart Process type to create an item for. |
| Fields | A collection of fields to set on the new SPA item. Each field has: - Field Name: select which field to set. - Field Value: the value to assign. |
| Use JSON Format for Fields | Whether to provide the fields as a JSON object instead of individual field entries. |
| Fields (JSON) | The fields and their values specified in JSON format (used if "Use JSON Format for Fields" is true). |
Output
The node outputs an array of items, each containing a json property representing the created SPA item as returned by the Bitrix24 API. The structure typically includes the newly created item's fields and metadata.
If an error occurs and "Continue On Fail" is enabled, the output will contain an error object with:
error: The error message.resource: The resource name ("spa").timestamp: The ISO timestamp of the error occurrence.
No binary data output is indicated.
Dependencies
- Requires connection to Bitrix24 with one of the supported authentication methods: OAuth2, Webhook URL, or API Key.
- Uses Bitrix24 API endpoints related to Smart Process Automation (
crm.item.fields,crm.type.list, etc.). - Requires proper permissions in Bitrix24 to create SPA items.
- No additional external services beyond Bitrix24 API are needed.
Troubleshooting
Common Issues:
- Incorrect or missing SPA Type ID: The node requires a valid SPA type to create an item.
- Invalid field names or values: Fields must correspond to those available for the selected SPA type.
- Authentication failures: Ensure the chosen authentication method is correctly configured and authorized.
- API rate limits or connectivity issues with Bitrix24.
Error Messages:
- Errors during field loading or SPA type retrieval will be shown as options with descriptions indicating failure reasons.
- Runtime errors during execution will throw messages that can be captured if "Continue On Fail" is enabled.
Resolutions:
- Verify SPA types and fields exist and are accessible.
- Check authentication credentials and permissions.
- Use the "Use JSON Format for Fields" option carefully; ensure JSON syntax is correct.
- Review Bitrix24 API limits and network connectivity.