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
The node integrates with the Bitrix24 platform, specifically enabling interaction with its Document Generator resource. The "Get Document" operation retrieves a generated document by its unique ID from Bitrix24. This is useful in workflows where you need to fetch and process documents created within Bitrix24, such as contracts, invoices, or reports.
Practical examples include:
- Automatically retrieving a contract document after it has been generated for further processing or storage.
- Fetching an invoice document to send it via email or upload it to another system.
- Accessing generated reports for analysis or archival.
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 retrieve. |
| Options | Additional optional parameters; currently supports specifying an Access Token for authentication. |
Output
The node outputs JSON data representing the retrieved document's details. The exact structure depends on the Bitrix24 API response but typically includes metadata and content information about the document.
If the document contains binary data (e.g., the actual file content), it would be included in the output's binary property, allowing subsequent nodes to handle file downloads or uploads.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- The node relies on Bitrix24's API endpoints to fetch document data.
- Proper configuration of authentication credentials in n8n is necessary for successful API calls.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect Document ID causing "not found" errors.
- Network connectivity issues preventing API communication.
Error Messages:
- Errors thrown during execution will include the error message from Bitrix24 API.
- If "Continue On Fail" is enabled, errors are returned in the output JSON under an
errorfield along with the resource name and timestamp.
Resolutions:
- Verify and refresh authentication credentials.
- Confirm the Document ID is correct and the document exists.
- Check network access and proxy settings if applicable.