Actions31
- Company Actions
- Contact Actions
- Deal Actions
- Item Actions
- Lead Actions
- User Custom Method Actions
Overview
This node integrates with the Bitrix24 REST API to perform operations on CRM contacts. Specifically, the "Get" operation for the "Contact" resource retrieves detailed information about a single contact record by its unique ID. This is useful in scenarios where you need to fetch up-to-date contact data from Bitrix24 within an automation workflow, such as syncing contact details to another system, triggering follow-up actions based on contact info, or displaying contact data dynamically.
Example use cases:
- Retrieve a contact's full profile before sending a personalized email.
- Fetch contact details to update a customer support ticket.
- Use contact data to enrich records in a marketing automation platform.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24 API. Options: OAuth2, Webhook |
| ID | The unique identifier of the contact record to retrieve (required). Example: "12345" |
Output
The node outputs JSON data representing the contact record retrieved from Bitrix24. This typically includes fields such as contact name, phone numbers, emails, company association, and other CRM-specific attributes defined in Bitrix24.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the contact, but this is not evident from the provided code.
Dependencies
- Requires valid authentication credentials for Bitrix24, either via OAuth2 or Webhook method.
- The node depends on Bitrix24 REST API availability and correct permissions to access contact data.
- No additional external dependencies are indicated beyond standard n8n credential configuration.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens will cause authorization errors.
- Providing an incorrect or non-existent contact ID will result in a "record not found" error.
- Network connectivity problems can prevent API calls from succeeding.
Error messages and resolutions:
- Unauthorized / 401 errors: Check that the API credentials are correctly configured and have not expired.
- Not Found / 404 errors: Verify the contact ID exists in Bitrix24 and is correctly entered.
- Timeouts or network errors: Ensure stable internet connection and Bitrix24 API endpoint accessibility.