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 managing document templates within the Document Generator resource. The "Delete Template" operation allows users to remove a specified document template from their Bitrix24 account.
Common scenarios for this node include:
- Automating cleanup of outdated or unused document templates.
- Managing document lifecycle by programmatically deleting templates no longer needed.
- Integrating template management into broader workflows that maintain document consistency.
For example, a user might set up an automation that deletes a document template after a project is completed or when a template is replaced by a newer version.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook, API Key. |
| Template ID | The unique identifier of the document template to delete. Required for this operation. |
Output
The node outputs JSON data representing the result of the delete operation. If successful, the output typically confirms deletion; if an error occurs, the output includes an error message and metadata such as the resource name and timestamp.
Example output structure on failure:
{
"error": "Error message here",
"resource": "documentGenerator",
"timestamp": "2024-06-01T12:00:00.000Z"
}
No binary data output is involved in this operation.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, webhook URL, or API key.
- Proper credentials must be configured in n8n for the chosen authentication method.
- The node relies on Bitrix24's API endpoints for document template management.
Troubleshooting
Common issues:
- Invalid or missing Template ID will cause the operation to fail.
- Authentication failures due to incorrect or expired credentials.
- Insufficient permissions in Bitrix24 to delete document templates.
- Network connectivity issues preventing API calls.
Error messages and resolutions:
"Invalid Template ID": Verify the Template ID is correct and exists in Bitrix24."Authentication failed": Check that the API key, OAuth2 token, or webhook URL is valid and has not expired."Permission denied": Ensure the authenticated user has rights to delete document templates."Network error": Confirm network access to Bitrix24 API endpoints.
Using the node's "Continue On Fail" option can help handle errors gracefully in workflows.