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 users to send SMS messages via the "Message Service" resource and its "Send Message" operation. It supports multiple authentication methods including OAuth2, webhook URLs, and API keys, providing flexibility depending on security needs and environment.
Typical use cases include:
- Sending SMS notifications or alerts to customers or team members.
- Automating communication workflows within CRM processes.
- Integrating SMS messaging into business automation pipelines.
For example, a sales team could automatically send SMS reminders to clients about upcoming meetings or payment deadlines using this node.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL, or API Key. |
| Phone Number | The recipient's phone number in international format (e.g., +1234567890). |
| Message Text | The text content of the SMS message to be sent. |
| Additional Options | Optional parameters: • Provider ID: Specify which SMS provider to use. • From: Sender name or number displayed on the recipient's device. |
Output
The node outputs JSON data representing the result of the SMS sending operation. This typically includes confirmation details such as message status or any error information if the sending failed.
If an error occurs and the node is configured to continue on failure, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.
The node does not output binary data.
Dependencies
- Requires access to a Bitrix24 account with appropriate permissions.
- Needs one of the following authentication credentials configured in n8n:
- An OAuth2 credential for Bitrix24.
- A Bitrix24 webhook URL.
- An API key credential for Bitrix24.
- Network connectivity to Bitrix24 API endpoints.
Troubleshooting
Common issues:
- Incorrect or missing authentication credentials will cause authorization failures.
- Invalid phone number format may lead to message delivery errors.
- Specifying an unsupported or incorrect SMS provider ID might cause the message not to send.
Error messages:
- Authorization errors: Check that the selected authentication method is correctly configured and valid.
- API call failures: Verify network connectivity and Bitrix24 service availability.
- Validation errors: Ensure required fields like phone number and message text are provided and correctly formatted.
To handle errors gracefully, enable the "Continue On Fail" option so the workflow can proceed even if sending fails, capturing error details in the output.