Actions25
Overview
This node interacts with the Bitrix24 CRM system to manage "Deal" records. Specifically, the "List" operation retrieves multiple deal records from Bitrix24. It supports fetching all deals or limiting the number of returned deals and allows selecting specific fields to be included in the output.
Common scenarios where this node is useful include:
- Synchronizing deal data from Bitrix24 into another system.
- Generating reports or dashboards based on current deals.
- Automating workflows that depend on deal information, such as sending notifications for new or updated deals.
For example, a user might configure the node to list all deals with only their ID, title, and stage fields to feed into a sales performance dashboard.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to retrieve all deal records (true) or limit the number of records (false). |
| Limit | The maximum number of deal records to return when "Return All" is false. |
| Select Fields | The specific fields of the deal records to retrieve. Multiple fields can be selected. |
Output
The node outputs an array of JSON objects representing deal records retrieved from Bitrix24. Each object contains key-value pairs corresponding to the requested fields of a deal.
If binary data were involved, it would be summarized here, but this node only returns JSON data related to deal records.
Dependencies
- Requires an API authentication token configured via credentials to access the Bitrix24 webhook URL.
- Uses HTTP POST requests to Bitrix24's REST API endpoints for CRM deal operations.
- The webhook URL must be correctly set in the credentials to form valid API request URLs.
Troubleshooting
- Missing Credentials: If no API credentials or webhook URL are provided, the node will throw errors indicating these are required.
- Invalid Webhook URL: An incorrect or missing webhook URL will cause API calls to fail.
- API Errors: If Bitrix24 returns errors (e.g., invalid parameters), these will be surfaced in the node output if "Continue On Fail" is enabled; otherwise, execution stops with an error.
- Field Selection Issues: Selecting fields that do not exist or are not accessible may result in incomplete or empty results.
- Limit vs Return All: Setting "Return All" to false but not specifying a reasonable "Limit" may lead to unexpected small result sets.
To resolve common issues:
- Verify API credentials and webhook URL correctness.
- Ensure selected fields exist in the Bitrix24 deal schema.
- Use "Return All" carefully to avoid large data loads.