Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node integrates with the Bitrix24 platform, allowing users to interact with various Bitrix24 resources and operations. Specifically, for the Message Service resource and the Get Providers operation, it retrieves information about available SMS providers configured in Bitrix24. This can be useful for workflows that need to send SMS messages via Bitrix24's messaging infrastructure or manage SMS provider settings.

Practical examples include:

  • Fetching a list of SMS providers before sending messages to select the appropriate provider dynamically.
  • Automating SMS notifications by first verifying available providers.
  • Integrating Bitrix24 SMS capabilities into broader automation workflows.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler but less secure), API Key.
Additional Options Collection of optional parameters:
β€’ Provider ID: Specify a particular SMS provider to use.
β€’ From: Sender name or number to appear on sent messages.

Output

The node outputs an array of items where each item's json property contains data returned from Bitrix24 related to the requested resource and operation. For the "Get Providers" operation under "Message Service," the output JSON will typically include details about SMS providers such as their IDs, names, and configuration details.

If an error occurs during execution, and the node is set to continue on failure, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.

No binary data output is indicated for this operation.

Dependencies

  • Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
  • The node depends on Bitrix24's API endpoints to fetch data.
  • No additional external services are required beyond Bitrix24 itself.
  • Proper configuration of credentials in n8n is necessary for successful API calls.

Troubleshooting

  • Common Issues:

    • Incorrect or expired authentication credentials leading to authorization errors.
    • Network connectivity issues preventing access to Bitrix24 API.
    • Specifying an invalid or non-existent Provider ID in additional options.
  • Error Messages:

    • Errors thrown by the node will include the message from Bitrix24 API responses.
    • If the node is configured to continue on fail, errors will be returned in the output JSON with fields error, resource, and timestamp.
  • Resolutions:

    • Verify and refresh authentication credentials.
    • Check network connectivity and firewall settings.
    • Ensure the Provider ID specified exists and is correctly formatted.
    • Review Bitrix24 API limits and permissions.

Links and References

Discussion