Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
The Bitrix24 node allows users to interact with the Bitrix24 CRM and business platform within n8n workflows. Specifically, the "CRM" resource with the "Get All" operation enables retrieving multiple records of various CRM entities such as contacts, deals, leads, companies, quotes, invoices, products, and activities.
This node is beneficial when you want to automate data retrieval from Bitrix24 for reporting, synchronization with other systems, or bulk processing of CRM data. For example, you could use it to fetch all contacts created after a certain date, or retrieve all deals sorted by their creation date.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key authentication |
| Entity | The type of CRM entity to work with. Options: - Contact - Deal - Lead - Company - Quote - Invoice - Product - Activity |
| Options | Additional parameters to customize the request: - Select: Fields to return, specified as a JSON array or comma-separated string (e.g., ["ID","TITLE"] or ID,TITLE) - Filter: Filter criteria in JSON format (e.g., {"TITLE": "Test"}) - Order: Sort order in JSON format (e.g., {"DATE_CREATE": "DESC"}) - Access Token: Optional access token to override credentials for API requests |
Output
The node outputs an array of JSON objects representing the retrieved CRM records matching the query parameters. Each object contains fields corresponding to the selected entity's properties, such as ID, title, creation date, etc.
If an error occurs and "Continue On Fail" is enabled, the output will contain an object with an error field describing the issue, along with metadata like the resource name and timestamp.
The node does not output binary data.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
- The node internally uses Bitrix24 API endpoints to fetch CRM data.
- No additional external dependencies beyond standard Bitrix24 API access are required.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens can cause authorization errors.
- Incorrect filter or order JSON syntax may result in API errors.
- Requesting fields that do not exist on the selected entity may lead to empty results or errors.
Error messages:
- Errors returned from the Bitrix24 API will be propagated. If "Continue On Fail" is enabled, these appear in the output JSON under the
errorkey. - Typical errors include authentication failures, invalid parameters, or rate limiting.
- Errors returned from the Bitrix24 API will be propagated. If "Continue On Fail" is enabled, these appear in the output JSON under the
Resolutions:
- Verify and refresh authentication credentials.
- Ensure JSON strings for filters and ordering are correctly formatted.
- Use the node’s dynamic field loading features to select valid fields.