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
This node integrates with the Bitrix24 CRM and business platform, allowing users to interact with various Bitrix24 resources. Specifically, for the Document Generator resource with the Get Providers operation, it retrieves a list of available document providers from Bitrix24.
Common scenarios where this node is beneficial include automating document generation workflows within Bitrix24, such as fetching available templates or providers before generating contracts, invoices, or other documents dynamically. For example, a user might first get the list of document providers to present options in a UI or to select a provider programmatically for subsequent document creation steps.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Output
The node outputs an array of JSON objects representing the data returned by the Bitrix24 API for the requested resource and operation. For the Get Providers operation under the Document Generator resource, the output JSON typically contains information about document providers available in the Bitrix24 account.
The exact structure depends on the Bitrix24 API response but generally includes fields such as provider IDs, names, and possibly descriptions or metadata related to each document provider.
If the node supports binary data output (not indicated here), it would be summarized as providing relevant binary content associated with the operation, such as generated documents or files.
Dependencies
- Requires access to a Bitrix24 account with appropriate permissions.
- Needs one of the following authentication methods configured in n8n:
- OAuth2 credentials
- Webhook URL
- API Key credential
- The node relies on internal helper functions to make standard Bitrix24 API calls.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured and valid. OAuth2 tokens may expire and require refresh.
- API call failures: Network issues or incorrect permissions can cause API calls to fail. Verify connectivity and user rights in Bitrix24.
- Empty or unexpected results: If no providers are returned, confirm that document providers exist in the Bitrix24 account and that the API endpoint supports the requested operation.
- Continue on Fail: If enabled, the node returns error details in the output JSON instead of failing the workflow, which helps in debugging.