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 "Get Templates" operation of the Document Generator resource in this Bitrix24 node fetches document templates from a Bitrix24 account. This is useful for workflows that need to dynamically retrieve available document templates for further processing, such as generating documents based on CRM data or automating document-related tasks.
Common scenarios include:
- Automatically listing all active document templates filtered by entity type (e.g., Leads, Deals).
- Fetching templates to present options to users in subsequent workflow steps.
- Integrating with document generation processes where templates are selected programmatically.
Example: A sales automation workflow could use this node to get all active invoice templates and then generate invoices automatically when a deal is closed.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key. |
| Filter | Collection of filters to narrow down templates: |
| - Entity Type | Filter templates by entity type. Options: All, Lead, Deal, Contact, Company, Invoice. |
| - Active | Boolean to filter only active templates (true/false). |
| - Access Token | String token used for authentication if applicable. |
| Return All | Boolean indicating whether to return all results or limit the number of pages fetched. |
| Max Pages to Load | Number specifying the maximum pages to load when Return All is false (each page has up to 50 items). |
Output
The node outputs an array of JSON objects representing document templates matching the specified filters. Each item in the output contains template details as returned by the Bitrix24 API.
If the node supports binary data output (not explicitly shown here), it would typically represent generated documents or files related to templates. However, for this operation, the output is purely JSON data describing templates.
Dependencies
- Requires connection to a Bitrix24 account via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- The node depends on Bitrix24's API endpoints to fetch document templates.
- Proper credentials must be configured in n8n for authentication.
- Network access to Bitrix24 services is required.
Troubleshooting
- Authentication errors: Ensure the chosen authentication method is correctly set up with valid credentials or tokens.
- Empty results: Check filter settings; for example, filtering by an entity type with no templates will return empty.
- API rate limits or pagination issues: If not returning all templates, increase "Max Pages to Load" or enable "Return All".
- Error messages: The node may throw errors if the Bitrix24 API is unreachable or returns invalid responses. Verify network connectivity and API permissions.
- Continue On Fail: If enabled, errors will be returned as part of the output JSON instead of stopping execution.
Links and References
- Bitrix24 Official API Documentation
- n8n Documentation on Creating Custom Nodes
- Bitrix24 Document Generator Overview (for understanding templates)