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 interacts with the Bitrix24 platform, specifically providing access to various resources and operations within Bitrix24 CRM and business services. The "Message Service" resource with the "Get Provider Limits" operation allows users to retrieve SMS provider limits from Bitrix24.
Typical use cases include:
- Monitoring SMS sending limits for a specific SMS provider integrated into Bitrix24.
- Automating workflows that depend on SMS quota availability.
- Integrating Bitrix24 SMS provider data into external reporting or alerting systems.
For example, a user might configure this node to check the remaining SMS quota of a provider before sending marketing messages, ensuring they do not exceed allowed limits.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Provider ID | The identifier of the SMS provider whose limits are to be retrieved. |
| Additional Options | Optional parameters including: - Provider ID: Specific SMS provider to use for sending. - From: Sender name or number. |
Output
The node outputs JSON data containing the SMS provider limits information as returned by the Bitrix24 API. The exact structure depends on the API response but typically includes fields such as current usage, maximum allowed messages, reset times, etc.
If an error occurs and "Continue On Fail" is enabled, the output will contain an error object with:
error: Error message string.resource: The resource name ("messageservice").timestamp: ISO timestamp of the error occurrence.
No binary data output is indicated in the source code.
Dependencies
- Requires authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
- Relies on Bitrix24's internal API endpoints to fetch SMS provider limits.
- No additional external dependencies beyond standard n8n credential setup and Bitrix24 API access.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials may cause authorization failures.
- Incorrect or missing Provider ID will result in errors or empty responses.
- Network connectivity issues can prevent API calls from succeeding.
Error Messages:
- Errors thrown by the Bitrix24 API will be surfaced in the node output if "Continue On Fail" is enabled.
- Typical error messages include authentication failures, invalid parameters, or API rate limiting.
Resolution Tips:
- Verify that the chosen authentication method is correctly configured and valid.
- Ensure the Provider ID matches an existing SMS provider in your Bitrix24 account.
- Check network connectivity and Bitrix24 service status.
- Enable "Continue On Fail" to capture error details for debugging.
Links and References
- Bitrix24 Official Documentation
- Bitrix24 SMS Provider API Reference
- n8n documentation on Bitrix24 Integration