# Mailchimp

![Mailchimp_x_Intuit_Eyebrow_Logo_Black.png](https://assets.relyanceuat.xyz/images/docs/6006364761485/6006246045581.png)
Mailchimp is an all-in-one marketing platform designed and developed for businesses using email to reach out to their target markets. It helps organizations manage and talk to their clients, customers, and other interested parties featuring custom email templates and marketing campaigns.

In order to integrate Mailchimp with Relyance AI you will need to create an **Oauth2 / App Token** link.

#### In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the **Settings** Menu in the bottom left-hand side.
3. Select **Integrations**.
4. Click on the **Vendor Integration** tab.
5. Find the **Mailchimp** integration card and click it to open its connections.
6. Under **Authentication Method**, choose **Oauth2 / App Token**.
8. Click **Authenticate**.
9. This will bring up a login page on the Mailchimp site:
10. Login to Mailchimp. This will then confirm the Relyance AI to Mailchimp connection:
11. Click **Allow**.
12. At this point, you should see the following result on the Vendor Integrations page:

![Mailchimp-3.png](https://assets.relyanceuat.xyz/images/docs/6006364761485/6006504581773.png)

![Mailchimp-1.png](https://assets.relyanceuat.xyz/images/docs/6006364761485/6006490543629.png)

![Mailchimp-2.png](https://assets.relyanceuat.xyz/images/docs/6006364761485/6006523393421.png)

![Mailchimp-4.png](https://assets.relyanceuat.xyz/images/docs/6006364761485/6006598098829.png)

13. Congratulations, you are now connected to **Mailchimp**.

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A feature you enabled returns nothing.** Some scopes belong to a feature rather than to the connection: **Data subject requests** needs `Admin`. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. **Authorised, then empty.** The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.

<!-- failure-modes:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

The **OAuth (browser authorization)** method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (`terraform import relyance_integration_connection.example mailchimp/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

<!-- terraform-examples:end -->