> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/tools/configuration/integrations/sms.md).
# SMS
## SMS Integration
Tab **Tools -> Configuration -> Integrations -> SMS** allows you to configure sending SMS notifications from the system.
SMS messages are one of the available forms of notification integration. The list of supported integrations is being expanded with additional services and communication channels.
The system does not have its own SMS gateway - sending messages requires an account with an external SMS service provider and an active message package. Currently supported are:
* [SMSAPI](https://www.smsapi.pl/)
* [OVHcloud](https://www.ovhcloud.com/pl/)
### SMSAPI integration configuration
{% stepper %}
{% step %}
#### Preparing the SMSAPI account
Before configuring the integration, make sure the account has a sufficient number of SMS credits.
{% endstep %}
{% step %}
#### Adding a sender
In the SMSAPI panel, create a sender, for example:
* `eAuditor`
The sender name will be visible as the author of the sent SMS messages.
{% endstep %}
{% step %}
#### Generating an API token
In the SMSAPI panel, create an API token, and then paste it into the SMS integration configuration in eAuditor.
{% endstep %}
{% step %}
#### Adding SMS contacts
After saving the configuration:
* go to the tab **Integrations -> SMS**,
* add contacts together with the phone numbers of notification recipients.
{% endstep %}
{% step %}
#### Using the integration
After correct configuration, the system can send:
* alerts,
* notifications,
* automation messages,
* DLP events,
* other system messages in SMS form.
> NOTE: Using Polish characters (ą, ć, ę, ł, ń, ó, ś, ź, ż) significantly shortens the maximum length of a single SMS message. This may cause the message to be split into several SMS messages, which increases sending costs.
> {% endstep %}
> {% endstepper %}
### OVHcloud integration configuration
{% stepper %}
{% step %}
#### Preparing the OVHcloud account
Before configuring the integration, make sure the account has a sufficient number of SMS credits,
{% endstep %}
{% step %}
#### Creating an SMS account
In the OVHcloud panel, create an SMS service that will be used to send messages.
{% endstep %}
{% step %}
### Creating API credentials
You must generate the following API access credentials:
* identifier,
* password,
* SMS account.
These credentials will be required when configuring the integration in eAuditor.
{% endstep %}
{% step %}
#### Adding a sender
In the OVHcloud panel, configure the sender name, for example:
* `eAuditor`
{% endstep %}
{% step %}
#### Configuration in eAuditor.
In the SMS integration settings, specify:
* SMS account,
* API identifier,
* API password.
{% endstep %}
{% step %}
#### Adding SMS contacts
After saving the configuration:
* go to the tab **Integrations -> SMS**,
* add notification recipients together with their phone numbers.
{% endstep %}
{% step %}
#### Using the integration
After completing the configuration, the system can send SMS messages related to:
* system alerts,
* automation,
* DLP events,
* administrative notifications,
* other actions performed in the system.
{% endstep %}
{% endstepper %}
## Summary
The SMS integration allows you to extend the system with instant notifications sent directly to users' and administrators' phones. The solution is particularly useful in the case of:
* critical security alerts,
* DLP events,
* automations requiring a quick response,
* administrative notifications,
* emergency messages.
Thanks to integration with external SMS service providers, the solution can be flexibly adapted to your own needs and billing model. The system enables centralized management of recipients and the use of SMS messages in parallel with other notification channels, such as Teams, Slack, or Discord.
In practice, SMS remains one of the fastest and most noticeable communication channels - especially when a "critical alert" should not wait in an unread email inbox until Monday morning.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/tools/configuration/integrations/sms.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.