Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify 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" resource with the "Get" operation enables retrieving a single record by its ID from one of these entity types.
Common scenarios where this node is beneficial include:
- Fetching detailed information about a specific contact or lead for follow-up actions.
- Retrieving deal data to update sales pipelines or generate reports.
- Accessing company or invoice records to synchronize with other systems.
Practical example:
- A user wants to get the details of a contact with a known ID to enrich customer data in another application.
- Another use case is fetching a deal record to check its current stage before triggering an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| 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 type. |
Output
The node outputs JSON data representing the retrieved CRM record. The structure of the json output field corresponds directly to the fields of the selected entity type in Bitrix24, including standard and custom fields.
If the node supports binary data output (not indicated explicitly here), it would typically represent attachments or files related to the CRM record, but this node primarily returns JSON data.
Example output snippet (conceptual):
{
"ID": "123",
"NAME": "John Doe",
"EMAIL": "john.doe@example.com",
"PHONE": "+1234567890",
...
}
Dependencies
- Requires authentication credentials configured in n8n for Bitrix24, which can be OAuth2, webhook URL, or API key.
- Relies on Bitrix24's REST API endpoints to fetch CRM data.
- No additional external dependencies beyond Bitrix24 API access.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Incorrect or non-existent Record ID causing "record not found" errors.
- Network connectivity problems preventing API calls.
Error messages and resolutions:
"Failed to load CRM fields": Indicates issues fetching metadata; verify API access and permissions."record not found"or similar: Check that the Record ID is correct and exists in the specified entity.- Authentication errors: Reconfigure credentials ensuring they have sufficient permissions.
To handle failures gracefully, the node supports continuing on fail, returning error details in the output JSON.