Actions25
Overview
This node integrates with the Bitrix24 CRM system via its API, allowing users to create, retrieve, list, update, and delete CRM records for various resources such as Leads, Deals, Contacts, and Companies. The "Create" operation specifically enables the creation of new records by specifying custom fields and their values.
Common scenarios where this node is beneficial include automating CRM data entry from external sources, syncing data between systems, or programmatically managing CRM entities without manual input.
For example, you can use this node to automatically add new leads collected from a web form into Bitrix24, specifying relevant lead details dynamically.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of fields to set on the created record. Each field consists of: - Field Name: Selectable from available Bitrix24 CRM fields for the chosen resource. - Field Value: The value to assign to that field. |
The "Fields" property supports multiple entries, allowing setting multiple fields in one create operation.
Output
The node outputs an array of JSON objects corresponding to each input item processed. For the "Create" operation, each output object contains the response from the Bitrix24 API after attempting to create a record. This typically includes information about the newly created record, such as its ID and status.
No binary data output is produced by this node.
Dependencies
- Requires an active Bitrix24 API authentication credential configured in n8n, providing a valid webhook URL.
- Uses HTTP POST requests to Bitrix24's REST API endpoints constructed from the webhook URL and selected resource/operation.
- Relies on Axios library for HTTP communication.
Troubleshooting
- Missing Credentials or Webhook URL: The node will throw errors if no credentials are found or if the webhook URL is missing. Ensure the Bitrix24 API credential is properly set up with a valid webhook URL.
- Invalid Field Names or Values: If specified fields do not exist or have invalid values, the Bitrix24 API may return errors. Use the "Fields" dropdown which loads available fields dynamically to avoid typos.
- API Errors: Network issues or API limits may cause request failures. The node captures these errors and either stops execution or continues based on the "Continue On Fail" setting.
- Empty or Incorrect IDs: For operations requiring an ID (not applicable to Create), ensure the ID parameter is correctly provided.