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, enabling users to interact programmatically with various Bitrix24 resources. Specifically, for the Document Generator resource with the Get Template Fields operation, it retrieves the fields available in a document template within Bitrix24.
Common scenarios where this node is beneficial include:
- Automating document creation workflows by dynamically fetching template fields.
- Integrating Bitrix24 document templates into broader automation pipelines.
- Validating or mapping data fields before generating documents.
For example, a user might use this node to fetch all fields from a specific document template to populate those fields automatically with CRM data before generating a contract or invoice.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Note: The provided properties JSON only includes the "Authentication" property. Other properties related to selecting the Document Generator resource or specifying the template are defined elsewhere in the node but are not included here.
Output
The node outputs an array of items, each containing a json object representing the retrieved data from Bitrix24.
For the Get Template Fields operation, the output's json field contains the list of fields available in the selected document template. Each field typically includes:
- Field name or label
- Field ID or key
- Description including type and whether the field is required
If an error occurs during the retrieval, the output will contain an error object with:
error: The error message stringresource: The resource name ("Document Generator")timestamp: ISO timestamp of when the error occurred
The node does not output binary data.
Dependencies
Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended)
- Webhook URL authentication
- API Key authentication
The node depends on Bitrix24 API endpoints to fetch template fields and other resource data.
Requires proper configuration of credentials in n8n corresponding to the chosen authentication method.
Troubleshooting
Common Issues
- Authentication failures: Incorrect or expired credentials can cause API calls to fail.
- API rate limits: Bitrix24 may limit the number of API requests; excessive calls could result in errors.
- Missing or incorrect resource/operation parameters: If the resource or operation is not properly set, the node cannot process the request.
- Network connectivity issues: Problems connecting to Bitrix24 API endpoints will cause failures.
Error Messages
- Errors returned from Bitrix24 API calls are caught and returned as part of the output if "Continue On Fail" is enabled.
- Typical error messages include failure to load fields or invalid authentication.
- To resolve errors:
- Verify credentials and re-authenticate if necessary.
- Check that the selected resource and operation parameters are correct.
- Ensure network connectivity to Bitrix24 services.
- Review Bitrix24 API documentation for any changes or limitations.