Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
This node integrates with the Bitrix24 CRM and business platform, allowing users to interact with various CRM entities such as contacts, deals, leads, companies, quotes, invoices, products, and activities. Specifically, the CRM - Get operation retrieves a single record by its ID from the selected CRM entity.
Common scenarios where this node is beneficial include:
- Fetching detailed information about a specific contact or lead for further processing or automation.
- Retrieving deal data to update dashboards or trigger follow-up actions.
- Accessing company or invoice records to synchronize with other systems.
Practical example:
- A workflow that triggers when a new email arrives, uses this node to get the related contact's full details by their record ID, and then sends a personalized response.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Entity | The type of CRM entity to work with. Options: Contact, Deal, Lead, Company, Quote, Invoice, Product, Activity. |
| Record ID | The unique identifier of the record to retrieve within the selected entity. |
Output
The node outputs an array of items, each containing a json object representing the retrieved CRM record. The structure of the json output corresponds directly to the fields of the selected Bitrix24 CRM entity, including standard and custom fields.
If an error occurs and "Continue On Fail" is enabled, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
The node does not output binary data.
Dependencies
Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended for production use).
- Webhook URL authentication (simpler but less secure).
- API key authentication.
Proper credentials must be configured in n8n for the chosen authentication method.
The node relies on Bitrix24's REST API endpoints corresponding to the selected CRM entity.
Troubleshooting
Common issues:
- Invalid or missing Record ID: The node requires a valid record ID; ensure the ID exists in Bitrix24.
- Authentication failures: Verify that the provided credentials are correct and have sufficient permissions.
- Network or API errors: Temporary connectivity issues or API rate limits may cause failures.
Error messages:
- Errors returned from Bitrix24 API calls will be surfaced in the node's error output if "Continue On Fail" is enabled.
- Typical messages include "Record not found," "Unauthorized," or "Invalid authentication token."
Resolution tips:
- Double-check the Record ID and entity type.
- Confirm that the API credentials are valid and have access rights.
- If using webhook authentication, ensure the webhook URL is correct and active.
- Enable "Continue On Fail" to handle errors gracefully in workflows.