Actions25
Overview
This node integrates with the Bitrix24 CRM system to manage Leads. Specifically, the "List" operation retrieves multiple lead records from Bitrix24. It supports fetching all leads or limiting the number of returned records and allows selecting specific fields to optimize data retrieval.
Common scenarios include:
- Synchronizing lead data from Bitrix24 into another system.
- Generating reports or dashboards based on selected lead attributes.
- Automating workflows that require batch processing of lead information.
For example, a user might want to fetch all leads created in the last month but only retrieve their names and contact details to reduce payload size.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all lead records (true) or limit the number of records (false). |
| Limit | Maximum number of lead records to return when "Return All" is false. |
| Select Fields | Choose which lead fields to retrieve. This can be any subset of available lead properties. |
Output
The node outputs an array of JSON objects representing lead records retrieved from Bitrix24. Each object contains key-value pairs corresponding to the selected lead fields.
If binary data were involved (not in this operation), it would represent file attachments or media related to leads, but this operation deals solely with JSON data.
Dependencies
- Requires a valid Bitrix24 API webhook URL credential configured in n8n.
- Uses HTTP POST requests to Bitrix24's REST API endpoints for leads.
- No additional external dependencies beyond standard HTTP client libraries bundled with n8n.
Troubleshooting
- Missing Credentials: If the API webhook URL credential is not set or invalid, the node will throw an error indicating credentials are missing.
- Invalid Webhook URL: The node requires a proper Bitrix24 webhook URL; if absent or malformed, it will fail.
- API Errors: Network issues or incorrect permissions may cause API calls to fail. The node captures such errors and either stops execution or continues based on the "Continue On Fail" setting.
- Field Selection Issues: Selecting non-existent fields may result in empty or partial data. Ensure fields exist by using the field loader method.
- Limit vs Return All: Setting "Return All" to false but specifying a very high limit may still cause performance issues; use wisely.