> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-enrolment/fr/inscription/via-email/connectors.md).

# Connecteurs

Connectez des fournisseurs d’e-mail et des plateformes marketing pour envoyer des liens Wallet sécurisés.

Ces guides couvrent l'envoi d'e-mails depuis les propres outils d'une marque, tout en plaçant des liens sécurisés The Wallet Crew dans les modèles.

Lorsque The Wallet Crew doit envoyer elle-même les e-mails transactionnels (inscription, vérification, livraison de Carte), commencez par [Fournisseur d'e-mails](/connectors/fr/email-provider.md).

### Connecteurs d'e-mails transactionnels (The Wallet Crew envoie)

* [SendGrid](/connectors/fr/email-provider/sendgrid.md)
* [Mailchimp](/connectors/fr/email-provider/mailchimp.md) (Transactionnel / Mandrill)
* [Salesforce Marketing Cloud](/connectors/fr/email-provider/salesforce-marketing-cloud.md)
* [Adobe Marketing Cloud](/connectors/fr/email-provider/adobe-marketing-cloud.md)

### Outils marketing (la marque envoie et intègre les liens)

Ces intégrations sont généralement utilisées pour orchestrer les parcours et la personnalisation. La marque conserve un contrôle total sur la délivrabilité et les performances des campagnes, et place les liens The Wallet Crew derrière ses propres CTA.

* [Actito](/connectors/fr/marketing-automation/actito.md)
* [Klaviyo](/connectors/fr/marketing-automation/klaviyo.md)


---

# 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://docs.thewalletcrew.io/guides-enrolment/fr/inscription/via-email/connectors.md?ask=<question>&goal=<user_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.