Actions25
Overview
This node integrates with the Bitrix24 CRM system to perform various operations on CRM resources such as Leads, Deals, Contacts, and Companies. Specifically for the Company resource with the Update operation, it updates an existing company record in Bitrix24 by sending updated field data to the Bitrix24 API.
Typical use cases include:
- Automating updates of company information based on external triggers or workflows.
- Synchronizing company data from other systems into Bitrix24.
- Bulk updating multiple company records with new details like address, phone numbers, or custom fields.
For example, you might use this node to update a company's phone number or add a new custom attribute whenever a related event occurs in your workflow.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the company record to update. This is required to specify which record to modify. |
| Input Format | The format used to provide the fields to update. Options: - Form: Enter fields individually. - JSON: Provide all fields as a JSON object. |
| Fields (JSON) | When using JSON input format, this property accepts a JSON object representing the fields and their new values to update. |
| Fields | When using Form input format, this is a collection of fields to update. Each entry includes: - Field Name: The name of the company field to update. - Field Value: The new value for that field. |
Output
The node outputs an array of JSON objects corresponding to the results of the update requests. Each object typically contains the response from the Bitrix24 API for the update operation, including success confirmation or error details.
The output JSON structure generally looks like:
{
"result": {
"ID": "123",
"fields": {
"TITLE": "Updated Company Name",
"PHONE": [{"VALUE": "+1234567890", "VALUE_TYPE": "WORK"}],
...
}
}
}
If the update fails, the output will contain an error message describing the issue.
No binary data output is produced by this node.
Dependencies
- Requires a valid 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 REST API endpoints for updating records.
- The node expects the Bitrix24 API to be accessible and properly configured to accept requests.
Troubleshooting
- Missing Credentials or Webhook URL: The node throws errors if the API credentials or webhook URL are not set or invalid. Ensure these are correctly configured in n8n.
- Invalid Record ID: If the provided company ID does not exist, the API will return an error. Verify the ID before running the update.
- Malformed JSON Input: When using JSON input format, invalid JSON syntax will cause parsing errors. Validate JSON before submitting.
- Field Names or Values Not Accepted: Using incorrect field names or unsupported values may cause API errors. Use the node's dynamic field loading feature to select valid fields.
- API Rate Limits or Network Issues: Temporary failures communicating with Bitrix24 can occur. Check network connectivity and API limits.
Common error messages:
"Webhook URL is required!"— Set the webhook URL in credentials."No credentials got returned!"— Ensure API credentials are configured."Invalid response from Bitrix24!"— Check API availability and permissions."Failed to execute node: ..."— General catch-all for unexpected errors; inspect inner message.