Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with the Bitrix24 CRM platform, specifically enabling users to update existing CRM records. It supports updating various entity types such as contacts, deals, leads, companies, quotes, invoices, products, and activities within Bitrix24.

Typical use cases include:

  • Modifying contact details like phone numbers or email addresses.
  • Updating deal stages or categories.
  • Changing lead information or company data.
  • Adjusting custom fields on any supported CRM entity.

For example, a sales automation workflow could use this node to update a contact's phone number and email address after receiving new information from a form submission.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key.
Entity The type of CRM entity to update. Options: Contact, Deal, Lead, Company, Quote, Invoice, Product, Activity.
Record ID The unique identifier of the record to update in Bitrix24.
Fields A collection of fields to update on the selected entity. Each field consists of:
- Field Name: Selectable list of available fields based on the entity.
- Field Value: The value to set for that field.
Phone Numbers (Only for Contact, Lead, Company) Multiple phone numbers can be added or updated. Each phone number includes:
- Type: Work, Mobile, Home, Fax, Pager, Other.
- Phone Number: The actual phone number string.
Email Addresses (Only for Contact, Lead, Company) Multiple email addresses can be added or updated. Each email address includes:
- Type: Work, Home, Other.
- Email Address: The actual email string.

Output

The node outputs an array of items where each item contains a json object representing the response from Bitrix24 after attempting to update the specified record. This typically includes the updated record's data or confirmation of the update operation.

If the node encounters an error and is configured to continue on failure, it outputs an item with an error field describing the issue, along with the resource name and a timestamp.

The node does not output binary data.

Dependencies

  • Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, webhook URL, or API key.
  • Needs appropriate permissions in Bitrix24 to update CRM entities.
  • No additional external services are required beyond Bitrix24 itself.
  • The node uses internal helper functions to call Bitrix24 APIs and dynamically load available fields for entities.

Troubleshooting

  • Common issues:

    • Incorrect or missing Record ID will cause the update to fail.
    • Insufficient permissions or invalid authentication credentials will result in authorization errors.
    • Providing invalid field names or values may cause API errors.
    • Using webhook authentication might be less secure and could have limited capabilities compared to OAuth2.

  • Error messages:

    • Errors returned by Bitrix24 API will be included in the output if "Continue On Fail" is enabled.
    • Typical errors include "Record not found", "Access denied", or "Invalid field value".

  • Resolutions:

    • Verify the Record ID exists and is correct.
    • Ensure the authentication method is properly configured and has necessary scopes/permissions.
    • Validate field names and values against Bitrix24 CRM schema.
    • Prefer OAuth2 authentication for production environments for better security and reliability.

Links and References

Discussion