Actions25
Overview
This node integrates with the Bitrix24 CRM system to perform operations on various resources such as Deals, Leads, Contacts, and Companies. Specifically for the Deal - Get operation, it retrieves a single deal record by its ID from Bitrix24. Users can optionally specify which fields of the deal they want to retrieve.
Common scenarios where this node is useful include:
- Fetching detailed information about a specific deal in your sales pipeline.
- Retrieving selective data fields to minimize payload size or focus on relevant information.
- Integrating Bitrix24 deal data into workflows for reporting, notifications, or further processing.
Example: You have a workflow that triggers when a deal is updated elsewhere, and you want to fetch the latest details of that deal by its ID to update another system or send a notification.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the deal record to retrieve. This is required for the "Get" operation. |
| Select Fields | Optional list of specific fields to retrieve from the deal record. If left empty, all fields are returned. |
Output
The node outputs an array of JSON objects representing the retrieved deal records. For the "Get" operation, the output will contain one object with the deal's data fields as key-value pairs.
json: Contains the deal data fields as returned by the Bitrix24 API.- No binary data is output by this node.
Example output structure (simplified):
[
{
"ID": "123",
"TITLE": "Important Deal",
"STAGE_ID": "WON",
"OPPORTUNITY": "10000",
...
}
]
Dependencies
- Requires an active Bitrix24 API connection configured via an API authentication token or webhook URL credential.
- The node uses the Bitrix24 webhook URL to construct API endpoints dynamically.
- Axios library is used internally for HTTP requests.
Troubleshooting
No credentials got returned!
Ensure that the Bitrix24 API credentials (webhook URL or API token) are properly set up in n8n and linked to the node.Webhook URL is required!
The node requires a valid Bitrix24 webhook URL to function. Verify that the webhook URL is correctly configured in the credentials.Invalid response from Bitrix24!
This may indicate issues with the API endpoint or permissions. Check if the webhook URL has sufficient rights to access deal data.Error messages from API calls
Errors during API calls (e.g., invalid ID, permission denied) will be returned in the output if "Continue On Fail" is enabled; otherwise, the node execution will stop with an error.