Actions25
Overview
This node integrates with the Bitrix24 CRM system, specifically allowing operations on various resources such as Leads, Deals, Contacts, and Companies. For the Company resource with the Update operation, it updates an existing company record in Bitrix24 by specifying the record ID and the fields to update.
Typical use cases include:
- Automating updates to company information based on external triggers or workflows.
- Synchronizing company data from other systems into Bitrix24.
- Bulk updating multiple company records with new or corrected data.
For example, you might update a company's phone number or address after receiving updated contact details from another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the company record to update. |
| Fields | A collection of fields to update on the company record. Each field consists of: |
| - Field Name: The name of the company field to update (loaded dynamically from Bitrix24). | |
| - Field Value: The new value to set for that field. |
Output
The node outputs an array of JSON objects representing the response from the Bitrix24 API for each input item processed. For the update operation, the output typically includes:
- Confirmation of the update action.
- Any relevant metadata returned by Bitrix24 about the updated record.
The exact structure depends on Bitrix24's API response but generally contains success status and possibly the updated record ID.
No binary data is output by this node.
Dependencies
- Requires an active Bitrix24 API credential configured in n8n, which must provide a valid webhook URL for API access.
- Uses HTTP POST requests to Bitrix24 webhook endpoints corresponding to the resource and operation.
- Relies on Bitrix24's REST API availability and correct permissions for the authenticated user.
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 API key/credential is properly set up and includes the webhook URL.
- Invalid Field Names: If a field name does not exist or is incorrect, the API may reject the update. Use the dynamic field loader to select valid field names.
- API Errors: Network issues or permission problems can cause API calls to fail. Check connectivity and user permissions in Bitrix24.
- Continue On Fail: If enabled, the node will continue processing remaining items even if some fail, returning error messages per failed item.
Common error messages:
- "No credentials got returned!" — Set up the required API credentials.
- "Webhook URL is required!" — Ensure the webhook URL is included in the credentials.
- "Invalid response from Bitrix24!" — Possible API endpoint or permission issue.
Links and References
- Bitrix24 REST API Documentation
- Bitrix24 CRM Entities
- n8n documentation on Creating Custom Nodes