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 CRM and business platform, enabling users to perform various operations on Bitrix24 resources. Specifically, for the Document Generator resource with the Create Template operation, it allows users to create document templates within Bitrix24. This is useful in automating document creation workflows such as generating contracts, invoices, or proposals based on predefined templates.
Common scenarios include:
- Automatically creating document templates when new deals or leads are added.
- Managing document templates programmatically to keep them up-to-date.
- Integrating Bitrix24 document generation into broader automation workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Output
The node outputs an array of items where each item contains a json object representing the result of the operation performed on the selected resource. For the Create Template operation under the Document Generator resource, the output JSON will typically contain details about the newly created template, such as its ID, name, and other metadata returned by the Bitrix24 API.
If the node encounters an error and "Continue On Fail" is enabled, the output will include an error object with:
error: The error message string.resource: The resource name involved in the operation.timestamp: ISO timestamp of when the error occurred.
The node does not explicitly output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, Webhook URL, or API Key).
- Uses Bitrix24 API endpoints internally to perform actions.
- No additional external services beyond Bitrix24 are required.
- Proper credentials must be configured in n8n for the chosen authentication method.
Troubleshooting
- Authentication Errors: Ensure that the correct authentication method is selected and that credentials (OAuth tokens, webhook URLs, or API keys) are valid and have sufficient permissions.
- API Call Failures: Network issues or incorrect API parameters can cause failures. Check the error messages for details.
- Resource or Operation Not Supported: Selecting unsupported combinations may lead to errors; verify that the Document Generator resource supports the Create Template operation.
- Rate Limits: Bitrix24 API rate limits might cause temporary failures; implement retries or handle errors gracefully.
- Error Messages: When an error occurs, the node returns an error message in the output JSON if "Continue On Fail" is enabled. Use this message to diagnose issues.