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 create new Lead records in a Bitrix24 CRM system. It is designed for automating lead management workflows by programmatically adding leads based on input data. Common scenarios include capturing leads from web forms, syncing leads from other systems, or bulk importing lead data.
Practical examples:
- Automatically creating a lead when a new contact form submission is received.
- Importing leads from a CSV file by iterating over rows and creating leads one by one.
- Creating leads with custom fields populated dynamically from other workflow data.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method to connect to Bitrix24: OAuth2 or Webhook-based API key authentication. |
| Input Type | Select how to provide lead data: - Using Fields: Fill individual lead fields. - Using JSON: Provide raw JSON data representing the lead. |
| Fields | When "Using Fields" is selected, specify one or more field name-value pairs to set on the new lead. Field names can be chosen from available Bitrix24 lead fields or specified via expressions. |
| JSON Body | When "Using JSON" is selected, provide the complete lead data as a JSON object. |
Output
The node outputs the response from the Bitrix24 API after creating the lead. The main output is a JSON object containing details of the newly created lead, such as its ID and any other returned metadata.
If binary data were involved (not applicable here), it would be summarized accordingly, but this node deals only with JSON data.
Dependencies
- Requires access to a Bitrix24 account with API permissions to create leads.
- Requires an API authentication credential configured in n8n, either OAuth2 or webhook token.
- No additional external dependencies beyond the Bitrix24 REST API.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials and permissions.
- Invalid field names or values: When using individual fields, verify that field names match those supported by Bitrix24 leads. Use expressions carefully.
- Malformed JSON: If providing raw JSON, ensure it is valid and matches the expected structure for a lead in Bitrix24.
- API rate limits or connectivity issues: Check network connectivity and Bitrix24 API usage limits if requests fail intermittently.
- Error messages from Bitrix24 API: These typically indicate invalid data or permission issues; review the error message details and adjust input accordingly.
Links and References
- Bitrix24 REST API Documentation
- n8n Expressions Documentation (for dynamic field values)