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 allows users to interact with the Bitrix24 CRM and business platform. Specifically, the Chatbot - Send Message operation enables sending messages from a chatbot to a specified dialog or chat within Bitrix24. This is useful for automating communication workflows, such as sending notifications, alerts, or responses to users in Bitrix24 chats.
Practical examples include:
- Sending automated status updates to a team chat.
- Delivering customer support messages via a chatbot.
- Broadcasting announcements through a Bitrix24 chatbot.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key authentication |
| Bot ID | The unique identifier of the chatbot sending the message. |
| Dialog ID | The identifier of the dialog or chat where the message will be sent. |
| Message Text | The text content of the message to send. |
| Options | Additional optional parameters to customize the message or bot behavior: • Client ID • Open Line ID • Language ID • Bot Description • Bot Avatar URL • Command Description • Is Common (boolean) • Is Hidden (boolean) • Allow Extranet (boolean) • Message Type (Text or System) • Attachments (JSON array) • Keyboard Buttons (JSON array) • URL Preview (boolean) • Custom Parameters (JSON object) • Access Token (string) |
Output
The node outputs an array of items, each containing a json property with the response data from Bitrix24 after sending the message. The exact structure depends on the Bitrix24 API response but typically includes confirmation details about the sent message.
If an error occurs and "Continue On Fail" is enabled, the output item will contain an error field describing the issue, along with the resource name and a timestamp.
The node does not explicitly output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, webhook URL, or API key.
- Proper credentials must be configured in n8n for the chosen authentication method.
- Network access to Bitrix24 API endpoints is necessary.
Troubleshooting
- Authentication errors: Ensure that the correct authentication method is selected and that credentials (OAuth tokens, webhook URLs, or API keys) are valid and have sufficient permissions.
- Invalid Bot ID or Dialog ID: Verify that the provided IDs exist and the bot has permission to send messages in the specified dialog.
- Malformed JSON in attachments or keyboard buttons: When providing JSON for attachments or keyboard layout, ensure it is correctly formatted to avoid API errors.
- API rate limits or connectivity issues: Check network connectivity and Bitrix24 API usage limits if requests fail intermittently.
- Error messages in output: If the node returns an error in the output JSON, review the error message for clues and verify input parameters accordingly.