> For the complete documentation index, see [llms.txt](https://developers.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.didomi.io/integrations/emailing.md). # Emailing Use your own emailing providers for sending emails (authentication, consent changes, etc.) to your users The Didomi platform sends emails to your customers on your behalf in various use cases: authenticating a customer before allowing them to access their preferences, confirming consent changes, etc.\ \ By default, Didomi will send those messages with the email address `support@didomi.io` with our standard content. To customize those emails and send them from your own email address, you can configure Didomi to connect to your email provider or create your own templates using Didomi provider. The following providers are currently supported: * [Actito Email](/integrations/emailing/providers/actito-email.md) * [Actito SMS](/integrations/emailing/providers/actito-sms.md) * [Adobe Campaign Classic](/integrations/emailing/providers/adobe-campaign-classic.md) * [Adobe Campaign Standard](/integrations/emailing/providers/adobe-campaign-standard.md) You will need to [configure templates](/integrations/emailing/templates.md) for the emails that Didomi will send on your behalf. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developers.didomi.io/integrations/emailing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.