Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to interact with various Bitrix24 resources and operations. For the Message Service resource with the Get Message Status operation, it retrieves the status of a previously sent message by its ID. This is useful in scenarios where you need to track delivery or processing status of messages sent via Bitrix24's messaging services.

Practical examples include:

• Checking if an SMS or notification message was successfully delivered.
• Monitoring message states for audit or logging purposes.
• Triggering subsequent workflows based on message status updates.

Properties

Output

The node outputs JSON data representing the status information of the requested message. The exact structure depends on Bitrix24's API response but typically includes fields such as message state, timestamps, and any error or delivery details.

If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs a JSON object containing:

• error: The error message.
• resource: The resource name ("messageservice").
• timestamp: The time when the error occurred.

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 relies on Bitrix24's API endpoints to fetch message status.
• Proper configuration of credentials within n8n is necessary for successful API calls.

Troubleshooting

• Common Issues:

  • Invalid or expired authentication credentials leading to authorization errors.
  • Incorrect or non-existent Message ID causing "not found" or similar errors.
  • Network connectivity issues preventing API communication.
  • Using webhook authentication may be less secure and could lead to permission limitations.

• Error Messages:

  • Errors returned from Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
  • Typical errors include authentication failures, invalid parameters, or API rate limits.

• Resolutions:

  • Verify and refresh authentication credentials.
  • Confirm the Message ID is correct and corresponds to a sent message.
  • Check network access and firewall settings.
  • Prefer OAuth2 authentication for production environments for better security and reliability.

Links and References

• Bitrix24 Official API Documentation
• Bitrix24 Messaging API Reference
• n8n Documentation on Credentials