> 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/connectors/email-provider/mailchimp.md).

# Mailchimp

Configure The Wallet Crew to send its transactional emails through Mailchimp Transactional (Mandrill) instead of the default email provider.

The Wallet Crew can send transactional emails through Mailchimp Transactional (Mandrill). This covers messages like pass download links, verification emails, etc.

By default, The Wallet Crew uses **its own SendGrid account**. A brand can switch to **a dedicated Mailchimp Transactional account** to centralize email activity in Mandrill, or when Mandrill is already used for deliverability monitoring.

This setup is limited to transactional sending. It does not integrate Mailchimp Marketing features like audiences or campaigns.

If the right option is not obvious yet, start with [Email provider](https://docs.thewalletcrew.io/connectors/email-provider.md).

## Configure a dedicated Mailchimp Transactional (Mandrill) account

Before The Wallet Crew configuration is updated, make sure Mandrill can authenticate the sender identity. In practice, that means having a Mailchimp Transactional account, generating a Transactional API key, and validating the sender domain or email address to use.

{% stepper %}
{% step %}
**Decide which sender domain to use**

See [Decide which sender domain to use](https://docs.thewalletcrew.io/connectors/email-provider.md#decide-which-sender-domain-to-use).
{% endstep %}

{% step %}
**Create a Transactional API key**

Create an API key in Mailchimp Transactional (Mandrill), because The Wallet Crew uses it to call the Mandrill send APIs on the brand behalf.

<div data-with-frame="true"><figure><img src="https://3852727835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlP7d71aYydav6e0pRkxc%2Fuploads%2Fgit-blob-ca18994e5cf2a59ddd8722db2ba37ff27af22de5%2Fdocumentation-mailchimp-api-mailchimp-transactional.png?alt=media" alt="API configuration in Mailchimp Transactional." width="375"><figcaption><p>API configuration in Mailchimp Transactional.</p></figcaption></figure></div>

Follow this guide: [Generate your API key](https://mailchimp.com/developer/transactional/guides/quick-start/#generate-your-api-key).
{% endstep %}

{% step %}
**Update `/server/emails.yml`**

The provider and its API key can also be set in **Settings → General → Email provider** (**Mailchimp Transactional**). To edit the file directly, open the advanced configuration editor:

<p align="center"><a href="https://admin.thewalletcrew.io/tenant/~/settings/config/tenant-config" class="button secondary" data-icon="chevrons-right">Settings → Advanced → Advanced configuration</a></p>

Then create or edit `/server/emails.yml`:

{% code title="/server/emails.yml" %}

```yaml
provider:
  type: mailchimp
  apiKey: YOUR_MANDRILL_API_KEY
  from:
    email: no-reply@yourbrand.com
    name: Your Brand
resources:
  - /locales/emails/
```

{% endcode %}

Replace `YOUR_MANDRILL_API_KEY` with the Mandrill API key. Then set the `from` values to a sender identity that Mandrill accepts.

{% hint style="warning" %}
Treat the Mandrill API key like a password.

Do not paste it in tickets or screenshots.
{% endhint %}
{% endstep %}

{% step %}
**Save and test**

Save the file in the admin console to apply the provider change. Trigger a single transactional email from the usual flow, then confirm delivery in Mailchimp Transactional activity logs.
{% endstep %}
{% endstepper %}

## Troubleshooting

Most issues come from using the wrong key type or sending from an unverified identity. If email sending fails or nothing seems to change, start with these checks:

* **Mailchimp Marketing vs Transactional**: a **Transactional (Mandrill)** key is required.
* **401/403 from Mailchimp**: check the key, and that Transactional is enabled.
* **Emails not delivered**: verify the sender domain/email in Mailchimp Transactional.
* **Nothing changes after editing**: confirm `/server/emails.yml` was edited in the right tenant and saved.

## FAQ

<details>

<summary><strong>Is a paid Mailchimp add-on required?</strong></summary>

Yes. Mailchimp Transactional (Mandrill) is a paid add-on to a Standard or Premium Mailchimp Marketing plan, billed in blocks of transactional email credits. See [Mailchimp transactional email pricing](https://mailchimp.com/pricing/transactional-email/).

</details>


---

# 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/connectors/email-provider/mailchimp.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.
