Actions25
Overview
This node integrates with the Bitrix24 CRM system to manage Contact records. Specifically, the "Create" operation for the Contact resource allows users to add new contact entries into Bitrix24. It supports two input formats: a form-based field input and a JSON-based input, providing flexibility depending on user preference or data source.
Common scenarios where this node is beneficial include:
- Automating the addition of new contacts collected from web forms or other systems.
- Integrating external applications that generate contact data directly into Bitrix24.
- Bulk creation of contacts by feeding JSON arrays or structured form data.
For example, a marketing automation workflow could collect leads via a website form and use this node to create corresponding contacts in Bitrix24 automatically.
Properties
| Name | Meaning |
|---|---|
| Input Format | Choose between "Form" (individual fields input) or "JSON" (raw JSON object input) for the contact data. |
| Fields (JSON) | When using JSON input format, provide the contact fields as a JSON object. |
| Fields | When using Form input format, add multiple fields specifying the field name, communication type (if applicable), and value. Communication types include Work, Mobile, Home, Fax, Telegram, WhatsApp, Viber, Facebook, Skype, Other. Field names are dynamically loaded from Bitrix24's available contact fields. |
Output
The node outputs an array of JSON objects representing the response from Bitrix24 API after creating the contact(s). Each object contains the result of the creation request, typically including identifiers and status information returned by Bitrix24.
No binary data output is produced by this operation.
Dependencies
- Requires an active Bitrix24 API credential configured in n8n, which must include a valid webhook URL for API access.
- The node uses the Bitrix24 REST API endpoints to perform operations.
- Network connectivity to the Bitrix24 instance is required.
Troubleshooting
- Missing Credentials or Webhook URL: The node will throw errors if credentials are missing or the webhook URL is not set. Ensure the API key and webhook URL are correctly configured.
- Invalid JSON Input: When using JSON input format, malformed JSON will cause parsing errors. Validate JSON syntax before execution.
- Field Name or Value Issues: If specified field names do not exist in Bitrix24 or values are invalid (e.g., enumeration values not matching allowed options), the API may reject the request. Use the dynamic field loading feature to select valid fields.
- API Errors: Network issues or Bitrix24 API errors will be surfaced as error messages. Check API limits, permissions, and network connectivity.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details per item.
Links and References
- Bitrix24 REST API Documentation
- n8n Documentation on Creating Custom Nodes
- Bitrix24 Contact Fields Reference (for understanding available contact fields)
This summary is based solely on static analysis of the provided source code and property definitions.