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 interaction with its Document Generator feature. The Download Document operation allows users to download a generated document by specifying its unique Document ID. This is useful in workflows where documents are dynamically created within Bitrix24 (e.g., contracts, invoices, reports) and need to be retrieved for further processing, storage, or distribution.
Practical examples:
- Automatically downloading a contract document after it has been generated in Bitrix24 to attach it to an email.
- Retrieving an invoice PDF from Bitrix24 to upload it to a cloud storage service.
- Fetching generated reports for archival or analysis purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key |
| Document ID | The unique identifier of the generated document to download |
| Options | Additional optional parameters; currently supports specifying an Access Token for authentication |
Output
The node outputs the downloaded document data in the json output field. Typically, this will include metadata about the document and the document content itself. If the document is binary (e.g., PDF, DOCX), the node will provide the binary data accordingly, allowing subsequent nodes to handle file saving, uploading, or sending.
Dependencies
- Requires valid 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 fetch the document data.
- Proper configuration of authentication credentials in n8n is necessary.
- Optionally, an access token can be provided directly in the node’s options.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect Document ID causing "document not found" errors.
- Network connectivity problems preventing API calls.
Error messages and resolutions:
- Authorization failed: Verify that the authentication method and credentials are correctly configured and have sufficient permissions.
- Document not found: Confirm the Document ID is correct and that the document exists in Bitrix24.
- API call failed: Check network connection and Bitrix24 service status.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 Document Generator API
- OAuth2 Authentication Guide for Bitrix24 (available in Bitrix24 developer resources)