Actions25
Overview
This node integrates with the Bitrix24 CRM system to manage company records. Specifically, the Company - List operation retrieves multiple company records from Bitrix24. It supports fetching all records or a limited subset, optionally filtered by specified criteria, and allows selecting specific fields to return.
Common scenarios where this node is useful include:
- Synchronizing company data from Bitrix24 into another system.
- Generating reports or dashboards based on filtered company data.
- Automating workflows that depend on retrieving companies matching certain conditions (e.g., companies in a specific region or with a particular status).
Example use case: Retrieve all companies whose name contains "Tech" and select only their ID, title, and phone number fields for further processing.
Properties
| Name | Meaning |
|---|---|
| Return All | Boolean flag to return all matching company records without limit. |
| Limit | Maximum number of company records to return when "Return All" is false. |
| Use Filter | Boolean flag to enable filtering of company records based on specified filter fields. |
| Filter Fields | Collection of filter conditions; each includes: - Field Name: The company field to filter by. - Operation: Comparison operator (Equals, Not Equals, Greater Than, Less Than, Contains, Starts With, Ends With, In List, etc.). - Value: The value to compare against. |
| Select Fields | List of company fields to retrieve. If empty, default fields are returned. |
Output
The output is a JSON array of company records matching the query. Each record is an object containing the requested fields (or default fields if none selected). The structure depends on the fields selected but typically includes identifiers, names, contact details, and other company attributes.
No binary data output is produced by this operation.
Example output snippet:
[
{
"ID": "123",
"TITLE": "Tech Solutions Ltd.",
"PHONE": "+1234567890"
},
{
"ID": "124",
"TITLE": "Innovative Tech Inc.",
"PHONE": "+0987654321"
}
]
If no records match the filters, the output will be an empty array.
Dependencies
- Requires a valid Bitrix24 API authentication token configured in n8n credentials.
- Needs the Bitrix24 webhook URL to access the API endpoints.
- Uses the Bitrix24 REST API endpoints for company data retrieval.
- Network connectivity to Bitrix24 service must be available.
Troubleshooting
- Missing Credentials or Webhook URL: The node throws errors if the API credentials or webhook URL are not set or invalid. Ensure these are correctly configured in n8n.
- Invalid Filter Configuration: Incorrect filter field names or unsupported operations may cause API errors or empty results. Verify field names exist in Bitrix24 and operations are supported.
- API Rate Limits or Timeouts: Large data requests (especially with "Return All") might hit API limits or time out. Consider using filters or limiting the number of records.
- Empty Results: If no records are returned, check filter criteria and ensure data exists in Bitrix24 matching those filters.
- Error Messages: Errors from the Bitrix24 API are passed through; review error messages for hints (e.g., permission issues, malformed requests).
Links and References
- Bitrix24 REST API Documentation
- Bitrix24 Company Entity Fields
- n8n documentation on Using Credentials
- n8n community forums for Bitrix24 integration discussions
This summary is based solely on static analysis of the provided source code and property definitions.