Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
The node integrates with the Bitrix24 platform, specifically enabling interaction with its chat functionality. The "Send Message" operation under the "Chat" resource allows users to send messages to a specified chat within Bitrix24. This is useful for automating communication workflows, such as sending notifications, alerts, or updates directly into Bitrix24 chat channels or group chats.
Practical examples include:
- Automatically sending a message to a team chat when a new deal is created.
- Posting system alerts or reminders into a project chat.
- Sending customized messages with attachments or URL previews to clients or internal teams.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Chat ID | The unique identifier of the chat where the message will be sent. |
| Message | The text content of the message to send. |
| Additional Message Fields | Optional additional settings for the message: |
| - Attach | Attachments in JSON format to include with the message. |
| - System | Boolean flag indicating if the message is a system message. |
| - URL Preview | Boolean flag to enable or disable URL preview in the message. |
Output
The node outputs an array of items, each containing a json object representing the response from Bitrix24 after sending the message. The exact structure depends on Bitrix24's API response but typically includes details about the sent message such as message ID, status, timestamps, and any errors if occurred.
If the node encounters an error and "Continue On Fail" is enabled, it outputs an item with a json field containing an error message, the resource name, and a timestamp.
The node does not output binary data.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- Needs proper configuration of these credentials within n8n.
- Relies on Bitrix24's REST API endpoints for chat messaging.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Incorrect Chat ID causing message delivery failure.
- Malformed JSON in attachments resulting in API errors.
- Network connectivity issues preventing API calls.
Error Messages:
- Errors returned by Bitrix24 API are propagated; typical messages include authentication failures, invalid parameters, or permission denials.
- If "Continue On Fail" is enabled, errors are returned as part of the output JSON with an
errorproperty.
Resolutions:
- Verify and refresh authentication credentials.
- Confirm the Chat ID exists and is accessible by the authenticated user.
- Validate JSON syntax for attachments.
- Check network connectivity and firewall settings.