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 Bitrix24 node allows users to interact with the Bitrix24 CRM and business platform. Specifically, the "Document Generator" resource with the "Get Documents" operation enables retrieving documents managed within Bitrix24. This node is useful for automating workflows that require fetching documents from Bitrix24, such as generating reports, syncing document data with other systems, or triggering actions based on document content.
Practical examples include:
- Automatically downloading contract documents when a deal reaches a certain stage.
- Fetching invoice PDFs to attach them to emails sent via another service.
- Retrieving document metadata for audit or compliance workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key |
Note: The node also supports selecting different resources and operations, but here we focus on the Document Generator resource and Get Documents operation.
Output
The node outputs JSON data representing the documents retrieved from Bitrix24. The exact structure depends on the Bitrix24 API response for documents but typically includes fields such as document ID, creation date, modification date, author, and document content or metadata.
If binary data is included (e.g., actual document files), it would be provided in the binary output field, allowing further processing or saving of the document files.
Dependencies
- Requires an active connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Uses Bitrix24's REST API endpoints to fetch data.
- No additional external dependencies beyond standard n8n credentials and HTTP request capabilities.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials or tokens.
- API call failures: Network issues or incorrect permissions in Bitrix24 can cause API calls to fail. Verify API access rights and network connectivity.
- Empty or missing document data: Confirm that the requested documents exist and that the correct resource and operation parameters are set.
- Error messages in output: If the node returns error objects in the output JSON, check the error message for details. Using the "Continue On Fail" option can help handle errors gracefully in workflows.