Bitrix icon

Bitrix

Consume Bitrix24 REST API

Actions31

Overview

This node integrates with the Bitrix24 REST API to update a Company record. It allows users to modify existing company data by specifying the record ID and providing new values for one or more fields. This is useful in scenarios where you need to keep your CRM data up-to-date automatically, such as syncing external databases, updating company details after receiving new information, or automating routine data maintenance tasks.

For example, you might use this node to update a company's phone number or address after receiving updated contact info from a lead generation tool.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: either via OAuth2 or Webhook.
ID The unique identifier of the Company record to update.
Input Type How to provide the update data:
- Using Fields: specify individual fields and their values.
- Using JSON: provide the entire update payload as raw JSON.
Fields When using "Using Fields" input type: a collection of field name-value pairs to update on the Company record. Field names can be selected from available entity fields.
JSON Body When using "Using JSON" input type: the complete JSON object representing the update data for the Company record.

Output

The node outputs the response from the Bitrix24 API after attempting to update the Company record. The output is structured as JSON and typically contains the updated record's data or confirmation of the update operation. If the API returns any errors, those will also be included in the output JSON.

No binary data output is produced by this node.

Dependencies

  • Requires valid authentication credentials for Bitrix24, either via OAuth2 or Webhook.
  • The node depends on Bitrix24 REST API availability.
  • Proper configuration of authentication credentials within n8n is necessary.
  • No additional external dependencies beyond the Bitrix24 API and n8n credential setup.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens may cause authorization failures.
    • Providing an incorrect or non-existent Company ID will result in errors indicating the record was not found.
    • Malformed JSON in the "JSON Body" input can cause parsing errors.
    • Attempting to update read-only or restricted fields may cause API errors.

  • Error Messages:

    • Unauthorized / Authentication failed: Check that the API credentials are correctly configured and have not expired.
    • Record not found: Verify the Company ID is correct and exists in Bitrix24.
    • Invalid JSON: Ensure the JSON body is well-formed and matches the expected schema.
    • Field validation errors: Confirm that field names and values conform to Bitrix24 requirements.

Resolving these usually involves verifying credentials, checking input data correctness, and consulting Bitrix24 API documentation for field constraints.

Links and References

Discussion