Actions25
Overview
This node integrates with the Bitrix24 CRM system to manage "Deal" records. Specifically, the List operation retrieves multiple Deal records from Bitrix24, optionally applying filters and selecting specific fields. It supports returning all records or limiting the number of results.
Common scenarios include:
- Fetching a list of deals for reporting or analysis.
- Retrieving deals that match certain criteria (e.g., deals above a certain amount or created after a specific date).
- Selecting only relevant fields to optimize data processing downstream.
Example use case: A sales automation workflow that periodically fetches all open deals with a value greater than $10,000 to trigger follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Return All | Boolean flag to return all matching deal records without limit. |
| Limit | Maximum number of deal records to return when "Return All" is false. |
| Use Filter | Boolean flag to enable filtering of deal records based on specified conditions. |
| Filter Fields | Collection of filter conditions; each includes: |
| - Field Name: The deal field to filter by (loaded dynamically from Bitrix24). | |
| - Operation: Comparison operator such as Equals, Not Equals, Greater Than, Contains, etc. | |
| - Value: The value to compare the field against. | |
| Select Fields | List of deal fields to retrieve for each record. If empty, defaults to a predefined set of fields. |
Output
The output is an array of JSON objects representing Deal records retrieved from Bitrix24. Each object contains key-value pairs corresponding to the selected fields of a deal.
- If "Return All" is enabled, all matching deals are returned.
- Otherwise, the output respects the "Limit" property.
- If filters are applied, only deals matching those filters appear in the output.
- No binary data is output by this node.
Example output snippet:
[
{
"ID": "123",
"TITLE": "Big Deal",
"OPPORTUNITY": "15000",
"STAGE_ID": "WON"
},
{
"ID": "124",
"TITLE": "Small Deal",
"OPPORTUNITY": "5000",
"STAGE_ID": "PROGRESS"
}
]
Dependencies
- Requires an API authentication token credential for Bitrix24 with access to the CRM.
- Needs the Bitrix24 webhook URL configured in the credentials to make API calls.
- Uses the Bitrix24 REST API endpoints for deals (
crm.deal.list.json). - Relies on n8n's HTTP request capabilities via Axios for communication.
Troubleshooting
- Missing Credentials or Webhook URL: The node throws errors if the API credentials or webhook URL are not provided. Ensure these are correctly configured.
- Invalid Filter Fields: Filters must use valid field names and supported operations. Invalid filters may cause no results or errors.
- API Rate Limits or Connectivity Issues: Network problems or Bitrix24 API limits can cause request failures. Check connectivity and API usage quotas.
- JSON Parsing Errors: When using JSON input formats elsewhere in the node, malformed JSON will cause errors.
- Empty Results: If no deals match the filters or selection criteria, the output will be empty or contain an error message indicating no records found.