Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to add new entries to Bitrix24 Lists (iblocks). It is useful for automating the creation of list items within Bitrix24, such as adding records to custom or standard lists used in business processes. Typical scenarios include syncing data from other systems into Bitrix24 lists, automating task or inventory management, or populating CRM-related lists dynamically.

For example, a user might use this node to add a new contact or deal record to a Bitrix24 list whenever a form is submitted on their website, or to create a new item in a project tracking list when a new issue is logged in an external system.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler), or API Key
Iblock Type ID The identifier of the iblock type where the new list item will be added
Iblock Code The code of the iblock (list) to which the item will be added
Fields A collection of fields to set on the new list item; each field has a name and a value
Options Additional options including:
- Access Token Optionally specify an access token to override the one from credentials
- Filter JSON filter criteria (not typically used for add operation but available)
- Order JSON sort order (not typically used for add operation but available)
- Select Comma-separated list of fields to select (not typically used for add operation but available)

The Fields property allows specifying multiple field name-value pairs that define the data for the new list entry.

Output

The node outputs an array of JSON objects representing the result of the add operation. Each output item contains the response from Bitrix24 after attempting to add the list item, typically including identifiers and status information about the newly created entry.

If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with the error message, resource name, and timestamp.

The node does not output binary data.

Dependencies

  • Requires valid authentication with Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
  • Needs proper configuration of credentials in n8n corresponding to the chosen authentication method.
  • Relies on Bitrix24 API endpoints for list management.
  • No additional external dependencies beyond Bitrix24 API access.

Troubleshooting

  • Common issues:
    • Incorrect or expired authentication tokens leading to authorization errors.
    • Invalid or missing Iblock Type ID or Iblock Code causing API failures.
    • Improperly formatted field names or values resulting in rejected requests.
  • Error messages:
    • Authorization errors: Check that the authentication credentials are correct and have sufficient permissions.
    • Validation errors from Bitrix24 API: Verify that all required fields are provided and correctly named.
    • Network or connectivity issues: Ensure that the n8n instance can reach Bitrix24 endpoints.
  • To resolve errors, verify credentials, confirm field names against Bitrix24 list schema, and enable "Continue On Fail" to handle errors gracefully in workflows.

Links and References

Discussion