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 interacts with the Bitrix24 platform, specifically to retrieve all automation rules configured for a given document type or Smart Process. It is useful in scenarios where you want to programmatically access and manage automation workflows within Bitrix24 CRM or business processes.
For example, you might use this node to:
- List all automation rules applied to CRM deals to audit or analyze workflow configurations.
- Retrieve automation rules for Smart Processes to integrate or synchronize them with other systems.
- Filter and sort automation rules based on specific criteria to generate reports or trigger further actions.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: OAuth2 (recommended), Webhook (simpler but less secure), API Key. |
| Document Type | The type of document the automation rule applies to. Examples include CRM Deal, Lead, Contact, Company, Quote, Invoice, or Smart Process Automation entities. |
| Smart Process | When the Document Type is a Smart Process, select the specific Smart Process with automation enabled. |
| Options | Additional options for the request: |
| - Access Token | An optional access token to override credentials for API requests. |
| - Filter | JSON object to filter the query results, e.g., { "PROPERTY_VALUE": "yes" }. |
| - Order | JSON object specifying the sort order of results, e.g., { "ID": "ASC" }. |
Output
The node outputs an array of items, each containing a json field representing an automation rule retrieved from Bitrix24. Each item corresponds to one automation rule matching the query parameters.
The structure of each json output object depends on the Bitrix24 API response for automation rules but typically includes properties such as rule ID, name, conditions, actions, and related metadata.
If the node encounters an error and is set to continue on failure, it outputs an item with an error field describing the issue, along with the resource name and a timestamp.
The node does not output binary data.
Dependencies
- Requires valid authentication with Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
- Uses Bitrix24 REST API endpoints to fetch automation rules and related metadata.
- No additional external services are required beyond Bitrix24.
- Proper configuration of credentials in n8n is necessary for successful API calls.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens can cause authorization failures.
- Incorrect or unsupported document types may result in empty or error responses.
- Malformed JSON in the Filter or Order options can cause request errors.
- Network connectivity issues between n8n and Bitrix24 API endpoints.
Error Messages:
- Errors returned by the Bitrix24 API will be included in the output if "Continue On Fail" is enabled.
- Typical error messages include authentication failures, invalid parameters, or rate limiting.
Resolutions:
- Verify that the selected authentication method is correctly configured and active.
- Ensure the document type and Smart Process selections are valid and correspond to existing Bitrix24 entities.
- Validate JSON syntax in filter and order fields before execution.
- Check network connectivity and API availability.