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 operations on Smart Process Automation (SPA) types within Bitrix24. The "Delete Type" operation under the SPA resource allows users to delete a specified Smart Process type by its ID.
Common scenarios for this node include automating the management of custom business processes in Bitrix24, such as cleaning up obsolete SPA types or managing lifecycle events of SPA entities programmatically. For example, a user might automate the removal of deprecated SPA types after a project ends or integrate SPA type deletion into a broader workflow that manages CRM data cleanup.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| Type ID | The identifier of the Smart Process type to delete. This is selected from available SPA types loaded dynamically via the API. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of the deletion or an error message if the operation failed. The output structure includes:
json: An object containing the response from Bitrix24 regarding the deletion.- In case of failure and if "Continue On Fail" is enabled, the output will contain an
errorfield with the error message, theresourcename, and a timestamp.
No binary data output is produced by this operation.
Dependencies
- Requires access to a Bitrix24 account with appropriate permissions to manage SPA types.
- Requires one of the following authentication methods configured in n8n:
- OAuth2 credentials
- Webhook URL
- API key credential
- Uses Bitrix24 REST API endpoints related to SPA type management (
crm.type.listand related calls). - The node relies on internal helper functions to make standardized API calls to Bitrix24.
Troubleshooting
Common Issues:
- Invalid or missing Type ID: Ensure the Type ID corresponds to an existing SPA type.
- Insufficient permissions: The authenticated user must have rights to delete SPA types.
- Network or API errors: Connectivity issues or Bitrix24 service outages can cause failures.
Error Messages:
- Errors returned from Bitrix24 API will be included in the output JSON under the
errorfield if "Continue On Fail" is enabled. - If the node fails without continuing, the error will be thrown and visible in the workflow execution logs.
- Errors returned from Bitrix24 API will be included in the output JSON under the
Resolution Tips:
- Verify authentication credentials are correct and have necessary scopes/permissions.
- Confirm the SPA Type ID exists and is valid.
- Check network connectivity and Bitrix24 service status.
- Enable "Continue On Fail" to capture error details in output for debugging.