Actions31
- Company Actions
- Contact Actions
- Deal Actions
- Item Actions
- Lead Actions
- User Custom Method Actions
Overview
This node integrates with the Bitrix24 REST API, specifically targeting CRM resources such as Leads. The "Get Fields Description" operation for the Lead resource retrieves metadata about the fields available in a Lead entity within Bitrix24. This is useful for dynamically understanding what data can be accessed or manipulated in Leads, enabling users to build workflows that adapt to the current CRM schema.
Common scenarios include:
- Fetching field definitions to dynamically generate forms or UI elements.
- Validating input data against the available Lead fields before creating or updating records.
- Synchronizing external systems by mapping their data fields to Bitrix24 Lead fields.
For example, a user might use this node to get all Lead fields and their descriptions to create a custom integration that imports leads from another system while ensuring data consistency.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24 API. Options: - OAuth2 - Webhook |
Output
The node outputs JSON data containing the description of Lead fields retrieved from Bitrix24. This typically includes field names, types, labels, and other metadata describing each field's characteristics.
If binary data were involved (not indicated here), it would represent file attachments or similar content, but this operation focuses on JSON metadata only.
Dependencies
- Requires access to Bitrix24 REST API.
- Needs an authentication credential configured in n8n, either via OAuth2 or Webhook method.
- Proper permissions in Bitrix24 to read CRM Lead metadata.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured and authorized in Bitrix24.
- Permission issues: The API user must have rights to access CRM Lead fields; otherwise, the node may return authorization errors.
- API limits or connectivity problems: Network issues or Bitrix24 API rate limits can cause failures; verify connectivity and retry policies.
- Empty or unexpected output: Confirm that the Lead resource exists and contains fields in the Bitrix24 instance.