Actions25
Overview
This node integrates with the Bitrix24 CRM system to manage Lead records. Specifically, the "Create" operation for the Lead resource allows users to create new lead entries in their Bitrix24 account by specifying custom fields and their values.
Common scenarios where this node is beneficial include:
- Automating lead capture from web forms or other sources into Bitrix24.
- Integrating external marketing tools or databases to push new leads automatically.
- Streamlining sales workflows by programmatically adding leads based on triggers or events.
For example, a user can configure this node to create a lead with fields like "Name", "Email", and "Phone Number" whenever a new contact form submission occurs on their website.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of fields to set on the new lead record. Each entry includes: |
| - Field Name: The name of the lead field to set (loaded dynamically from Bitrix24). | |
| - Field Value: The value to assign to that field. |
The "Fields" property supports multiple entries, allowing setting multiple lead attributes during creation.
Output
The node outputs an array of JSON objects representing the responses from Bitrix24 API for each created lead. Each object typically contains information about the newly created lead, such as its unique ID and status.
No binary data output is produced by this node.
Dependencies
- Requires an active Bitrix24 API authentication token configured in n8n credentials.
- Needs the Bitrix24 webhook URL to access the CRM API endpoints.
- Uses HTTP POST requests to Bitrix24's REST API endpoints specific to the Lead resource.
Troubleshooting
- Missing Credentials or Webhook URL: The node will throw errors if the API credentials or webhook URL are not provided or invalid. Ensure these are correctly set up in n8n.
- Invalid Field Names: If a field name does not exist in Bitrix24 or is misspelled, the API may reject the request. Use the dynamic field loader to select valid fields.
- API Errors: Network issues or Bitrix24 service problems can cause request failures. Check connectivity and Bitrix24 service status.
- Continue On Fail Behavior: When enabled, the node captures individual errors per item instead of stopping execution, returning error messages in the output JSON.