Bitrix24 icon

Bitrix24

袪邪斜芯褌邪 褋 Bitrix24 API

袣芯薪褌邪泻褌 → 袨斜薪芯胁懈褌褜

AI-generated

Overview

This node interacts with the Bitrix24 API to perform CRUD operations on the Contact resource. It supports creating, updating, retrieving, listing, and deleting contacts in Bitrix24. The node is useful for automating contact management workflows, such as adding new contacts from form submissions, updating contact details, retrieving contact information by ID or filter, listing contacts with optional filters, and deleting contacts.

Use Case Examples

  1. Create a new contact with phone and email fields from form input.
  2. Update an existing contact's details using JSON input format.
  3. Retrieve a contact by ID or by applying filters on contact fields.
  4. List all contacts or a limited number with optional filtering criteria applied to fields like phone or email type (work, mobile, home, etc.).

Properties

Name Meaning
ID The unique identifier of the contact record. Required for update and delete operations.
inputFormat Specifies the input format for create and update operations. Can be 'form' for structured fields or 'json' for raw JSON input.
fieldsJson The contact fields provided as a JSON object. Used when inputFormat is 'json' for create and update operations.
fields The contact fields provided as structured form data. Supports multiple fields with name, value type (e.g., work, mobile), and value. Used when inputFormat is 'form' for create and update operations.

Output

JSON

  • id - The unique identifier of the contact record, returned after create or update operations.
  • fields - The fields of the contact record, including phone numbers, emails, and other contact details.
  • success - Indicates successful deletion of a contact record.
  • error - Error message returned if a contact record is not found or an operation fails.

Dependencies

  • Bitrix24 API authentication token or API key credential

Troubleshooting

  • Ensure the ID is provided for update and delete operations; missing ID will cause errors.
  • When using JSON input format, ensure the JSON is valid and correctly structured to match Bitrix24 contact fields.
  • If a contact is not found during get or delete operations, the node returns an error message indicating the record was not found.
  • For list operations with filters, ensure filter fields and operations are correctly specified to avoid empty results.
  • API rate limits or network issues may cause request failures; handle errors and retry as needed.

Links

Discussion