Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

The node integrates with the Bitrix24 platform, specifically enabling operations on various Bitrix24 resources. For the Document Generator resource and the Delete Document operation, this node deletes a generated document identified by its unique Document ID.

This functionality is useful in scenarios where automated workflows need to manage document lifecycle within Bitrix24, such as cleaning up obsolete or temporary documents after processing or archiving. For example, after generating and sending a contract document, you might want to delete it from Bitrix24 to maintain storage hygiene.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24:
- OAuth2 (recommended for production)
- Webhook (simpler but less secure)
- API Key
Document ID The unique identifier of the generated document to be deleted

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 contains an error message along with the resource name and a timestamp.

No binary data output is involved in this operation.

Example output on failure:

{
  "error": "Error message here",
  "resource": "documentGenerator",
  "timestamp": "2024-06-01T12:00:00.000Z"
}

Dependencies

  • Requires authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
  • Uses Bitrix24 API endpoints internally to perform document deletion.
  • No additional external services are required beyond Bitrix24 itself.

Troubleshooting

  • Common issues:

    • Invalid or missing Document ID will cause the delete operation to fail.
    • Incorrect or expired authentication credentials will prevent successful API calls.
    • Insufficient permissions in Bitrix24 for deleting documents may result in authorization errors.
  • Error messages:

    • Errors returned from Bitrix24 API will be propagated in the output JSON under the error field.
    • If the node is configured to continue on failure, errors will not stop workflow execution but will be included in the output for handling downstream.
  • Resolution tips:

    • Verify that the Document ID is correct and corresponds to an existing document.
    • Ensure the selected authentication method is properly configured and valid.
    • Check user permissions in Bitrix24 to confirm delete rights on documents.

Links and References

Discussion