Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
The node integrates with the Bitrix24 platform, specifically enabling operations on various Bitrix24 resources. For the Document Generator resource with the Delete Document operation, it allows users to delete a generated document by specifying its unique document ID.
This node is beneficial in automation workflows where documents created or stored in Bitrix24 need to be programmatically removed, such as cleaning up outdated contracts, removing test documents, or managing document lifecycle automatically.
Practical example:
- Automatically delete a document after it has been processed or approved elsewhere in your workflow.
- Remove documents linked to CRM records that have been deleted or archived.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key |
| Document ID | The unique identifier of the generated document to delete |
Output
The output JSON contains the result of the delete operation. Typically, this will include confirmation of deletion or an error message if the operation failed.
If the operation fails and "Continue On Fail" is enabled, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.
No binary data output is expected for this operation.
Dependencies
- Requires authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
- The node depends on Bitrix24's API endpoints to perform the delete operation.
- Proper configuration of the Bitrix24 credentials within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials can cause authorization failures.
- Providing an incorrect or non-existent Document ID will result in errors from the Bitrix24 API.
- Network connectivity issues may prevent successful API calls.
Error messages:
- Errors returned from Bitrix24 API will be included in the output if "Continue On Fail" is enabled.
- Typical error messages might indicate "Document not found," "Unauthorized," or "Invalid request."
Resolutions:
- Verify that the authentication method and credentials are correctly set up and valid.
- Double-check the Document ID for correctness.
- Ensure network access to Bitrix24 API endpoints is available.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 Document Generator API Reference (for detailed API methods related to documents)