Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify Actions
Overview
This 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 chats from other systems or processes.
Practical examples include:
- Automatically sending a message to a team chat when a new deal is created.
- Posting system alerts or reminders in a project chat.
- Sending customer support updates to a chat channel.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| 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 extra fields 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 confirmation details about the sent message.
If the node encounters an error and "Continue On Fail" is enabled, it outputs an item with a json field containing:
error: The error message.resource: The resource name ("chat").timestamp: The ISO timestamp when the error occurred.
The node does not output binary data.
Dependencies
- Requires access to a Bitrix24 account with appropriate permissions.
- Supports three authentication methods:
- OAuth2 authentication (recommended for production use).
- Webhook URL authentication (simpler but less secure).
- API key authentication.
- Proper configuration of credentials in n8n is necessary depending on the chosen authentication method.
Troubleshooting
Common issues:
- Invalid or missing Chat ID: Ensure the Chat ID is correct and accessible by the authenticated user.
- Authentication failures: Verify that the selected authentication method is correctly configured and valid.
- Malformed attachments JSON: If using attachments, ensure the JSON format is valid.
- Network or API errors: Check connectivity and Bitrix24 service status.
Error messages:
- Errors thrown by the Bitrix24 API are passed through; they usually indicate issues like invalid parameters or permission problems.
- If "Continue On Fail" is enabled, errors are returned as part of the output JSON for easier handling in workflows.