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
The Bitrix24 node integrates with the Bitrix24 CRM and business platform, enabling automation workflows to interact with various Bitrix24 resources. Specifically, the Open Lines - Send Message operation allows sending messages within an ongoing chat session in Bitrix24's Open Lines communication channels.
This operation is useful for automating customer support or sales conversations by programmatically sending messages to a specific chat session. For example, you can use it to send automated replies, notifications, or follow-ups to customers interacting via Bitrix24 Open Lines.
Practical scenarios include:
- Automatically sending a welcome message when a new chat session starts.
- Sending updates or alerts to a customer during a support interaction.
- Integrating external systems to push messages into Bitrix24 chats based on events.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL, or API Key. |
| Session ID | The unique identifier of the chat session where the message will be sent. |
| Message | The content text of the message to send in the chat. |
| Chat ID | The identifier of the specific chat within the session to which the message belongs. |
| Options | Additional optional parameters: - Filter: JSON object to filter results (usage context dependent). - Sort: JSON object defining sort order (usage context dependent). |
Output
The node outputs an array of items corresponding to the result of the API call to send the message. Each item contains a json property with the response data from Bitrix24, typically including confirmation details about the sent message.
If an error occurs and "Continue On Fail" is enabled, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
The node does not output binary data.
Dependencies
- Requires authentication credentials configured in n8n:
- OAuth2 token credential (recommended for production).
- Or a Bitrix24 webhook URL.
- Or an API key credential.
- Access to Bitrix24 API endpoints for Open Lines messaging.
- Proper permissions in Bitrix24 to send messages in Open Lines sessions.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials causing authorization failures.
- Incorrect Session ID or Chat ID leading to "not found" errors.
- Insufficient permissions to send messages in the specified chat.
- Malformed message content or exceeding allowed length limits.
Error messages:
- Authorization errors: Check that the selected authentication method is correctly configured and valid.
- Resource not found: Verify that the Session ID and Chat ID are correct and exist in Bitrix24.
- API rate limits or connectivity issues: Ensure network access and consider retry logic.
To resolve errors, verify credentials, confirm IDs, and check Bitrix24 user permissions.
Links and References
- Bitrix24 Open Lines API Documentation
- Bitrix24 Developer Documentation
- n8n Documentation on Credentials
This summary is based on static analysis of the provided source code and input properties definitions. It reflects the structure and intended usage of the Bitrix24 node's Open Lines Send Message operation without runtime execution.