Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with the Bitrix24 CRM and business platform, specifically enabling the creation of a new status within Bitrix24. The "Create Status" operation under the "Status" resource allows users to define custom statuses for various CRM entities such as deals, leads, or contacts.

Typical use cases include automating the addition of new workflow stages or status categories in Bitrix24 based on external triggers or processes. For example, when a new project phase is initiated in another system, this node can create a corresponding status in Bitrix24 to keep CRM data aligned.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key
Fields Collection of fields defining the new status to create:
- Entity ID Identifier of the entity type (e.g., DEAL_STAGE, LEAD_STATUS, CONTACT_TYPE) — Required
- Status ID Unique identifier for the new status — Required
- Name Display name of the status — Required
- Sort Order Numeric value determining the order of the status (default 100)
- Extra Additional parameters as a JSON object

Output

The node outputs an array of items where each item contains a json property representing the response from Bitrix24 after creating the status. This typically includes details about the newly created status such as its ID and confirmation of creation.

If an error occurs and the node is configured to continue on failure, the output will contain an item with an error message, the resource name, and a timestamp.

No binary data output is produced by this node.

Dependencies

  • Requires valid authentication credentials for Bitrix24 via one of the supported methods:

    • OAuth2 token
    • Webhook URL
    • API key

  • The node depends on Bitrix24's REST API endpoints to perform operations.

  • Proper configuration of credentials in n8n is necessary to enable successful API calls.

Troubleshooting

  • Common Issues:

    • Missing required fields (Entity ID, Status ID, or Name) will cause the API call to fail.
    • Incorrect authentication setup may result in authorization errors.
    • Invalid JSON format in the Extra field can cause parsing errors.

  • Error Messages:

    • Errors returned from Bitrix24 API are surfaced in the node output if "Continue On Fail" is enabled.
    • Typical errors include authentication failures, invalid parameters, or network issues.

  • Resolution Tips:

    • Verify all required fields are provided and correctly formatted.
    • Ensure the selected authentication method is properly configured with valid credentials.
    • Validate JSON syntax in the Extra field before execution.
    • Check network connectivity and Bitrix24 service status if API calls fail unexpectedly.

Links and References

Discussion