Actions25
Overview
This node integrates with the Bitrix24 CRM system to perform operations on various resources such as Leads, Deals, Contacts, and Companies. Specifically, for the Contact resource with the Get operation, it retrieves a single contact record by its ID from Bitrix24. Users can optionally specify which fields of the contact they want to retrieve.
Common scenarios where this node is beneficial include:
- Fetching detailed information about a specific contact in your CRM for further processing or automation.
- Integrating Bitrix24 contacts data into other workflows or systems.
- Selectively retrieving only certain fields to optimize data usage and performance.
Example: You have a workflow that triggers when a new email arrives, and you want to fetch the corresponding contact details from Bitrix24 by their contact ID to personalize your response.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the contact record to retrieve. This is required for the Get operation. |
| Select Fields | Optional list of fields to retrieve for the contact. If left empty, all available fields are returned. The options are dynamically loaded from Bitrix24 and represent the contact's field names. |
Output
The node outputs an array of JSON objects representing the retrieved contact records. For the Get operation on Contact, the output JSON structure corresponds to the Bitrix24 API response for a single contact, including the requested fields.
Example output JSON snippet:
{
"result": {
"ID": "123",
"NAME": "John",
"LAST_NAME": "Doe",
"EMAIL": [{"VALUE": "john.doe@example.com", "VALUE_TYPE": "WORK"}],
...
}
}
No binary data output is produced by this node.
Dependencies
- Requires a valid Bitrix24 API authentication credential configured in n8n, providing access to the Bitrix24 webhook URL.
- Uses HTTP POST requests to Bitrix24 REST API endpoints via the webhook URL.
- The node dynamically loads available fields for selection from the Bitrix24 API.
Troubleshooting
- Missing Credentials or Webhook URL: The node will throw errors if the Bitrix24 API credentials or webhook URL are not set or invalid. Ensure these are correctly configured.
- Invalid Contact ID: Providing a non-existent or incorrect contact ID will result in an error or empty response. Verify the ID before running the node.
- Field Selection Issues: Selecting fields that do not exist or are not accessible may cause errors. Use the dynamic field loader to select valid fields.
- API Rate Limits or Network Errors: Network issues or Bitrix24 API rate limits can cause request failures. Implement retry logic or handle errors gracefully using the node’s "Continue On Fail" option.