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 and interaction with various Bitrix24 resources. Specifically, the Chatbot - Answer Command operation allows the node to respond to a chatbot command by sending a message as an answer to that command within Bitrix24.
This operation is useful in scenarios where you want to automate chatbot responses based on commands received in Bitrix24 chats. For example, you can create custom chatbot commands that trigger workflows or provide automated replies, such as answering FAQs, providing status updates, or executing specific business logic when a user issues a command in a chat.
Practical examples:
- Automatically reply to a "/status" command with the current project status.
- Respond to a "/help" command with a list of available commands or instructions.
- Send dynamic data fetched from other systems as a chatbot response triggered by a command.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used for authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication. |
| Bot ID | The unique identifier of the chatbot that will send the answer message. |
| Command ID | The unique identifier of the chatbot command to which this message is responding. |
| Message Text | The text content of the message that will be sent as the answer to the command. |
| Options | Additional optional parameters to customize the request, including: β’ 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 processing the command answer. The exact structure depends on the Bitrix24 API response but typically includes confirmation of the message sent or error details if the operation failed.
If the node encounters an error and "Continue On Fail" is enabled, it outputs an item with an error field describing the issue, along with the resource name and a timestamp.
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 process chatbot commands and send messages.
- Proper configuration of authentication credentials in n8n is necessary.
- Optional parameters like access tokens or client IDs may be required depending on the Bitrix24 setup.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials causing authorization failures.
- Incorrect Bot ID or Command ID leading to errors or no response.
- Malformed JSON in attachments, keyboard buttons, or custom parameters causing API request failures.
- Network connectivity issues preventing communication with Bitrix24 API.
Error Messages:
- Errors returned from Bitrix24 API are passed through in the output under the
errorfield. - If the node throws exceptions, enabling "Continue On Fail" allows workflow continuation with error details included in output.
- Errors returned from Bitrix24 API are passed through in the output under the
Resolutions:
- Verify and refresh authentication credentials.
- Double-check Bot ID and Command ID values.
- Validate JSON syntax for complex option fields.
- Ensure network access to Bitrix24 endpoints.