The MailChimp connector lets you perform insert, delete, update, and read operations on MailChimp dataset.
Before using the MailChimp connector, do the following tasks:
roles/secretmanager.viewerroles/secretmanager.secretAccessorA service account is a special type of Google account intended to represent a non-human user that needs to authenticate and be authorized to access data in Google APIs. If you don't have a service account, you must create a service account. The connector and the service account must belong to the same project. For more information, see Creating a service account.
secretmanager.googleapis.com (Secret Manager API)connectors.googleapis.com (Connectors API)To understand how to enable services, see Enabling services.
If these services or permissions have not been enabled for your project previously, you are prompted to enable them when configuring the connector.
For more information about setting up the MailChimp account, see Account Login.
For more information about generating a MailChimp API Key, see Generate API Key.
For more information about generating OAuth Credentials for MailChimp account, see GenerateOAuth Credentials.
A connection is specific to a data source. It means that if you have many data sources, you must create a separate connection for each data source. To create a connection, do the following:
For the list of all the supported regions, see Locations.
Connection names must meet the following criteria:
Error.
A node is a unit (or replica) of a connection that processes transactions. More nodes are required to process more transactions for a connection and conversely, fewer nodes are required to process fewer transactions. To understand how the nodes affect your connector pricing, see Pricing for connection nodes. If you don't enter any values, by default the minimum nodes are set to 2 (for better availability) and the maximum nodes are set to 50.
If you want to establish a private connection to your backend system, do the following:
This section lists the sample values for the various fields that you configure when creating the MailChimp connection.
All the Integration Connectors provide a layer of abstraction for the objects of the connected application. You can access an application's objects only through this abstraction. The abstraction is exposed to you as entities, operations, and actions.
However, it is possible that a connector doesn't support or have any entities, in which case the
Entities list will be empty.
Selecting an entity from the available list, generates a list of
operations available for the entity. For a detailed description of the operations, see the Connectors task's
entity operations.
However, if a connector doesn't support any of the entity operations, such unsupported
operations aren't listed in the Operations list.
Actions list will be empty.
The MailChimp connector can process 6 transactions per second, per node, and throttles any transactions beyond this limit. By default, Integration Connectors allocates 2 nodes (for better availability) for a connection.
For information on the limits applicable to Integration Connectors, see Limits.
This section lists the actions supported by the connector. To understand how to configure the actions, see Action examples.
Send a test email for a MailChimp campaign.
| Parameter Name | Data Type | Required | Description |
|---|---|---|---|
| CampaignID | string | True | The ID of the campaign to test. |
| TestEmails | string | True | A comma-separated list of emails to send. |
| SendType | string | True | The type of test email to send. Either html or plaintext The allowed values are html, plaintext. The default value is html. |
For example on how to configure the CampaignTest action,
see Action examples.
Send a MailChimp campaign.
| Parameter Name | Data Type | Required | Description |
|---|---|---|---|
| CampaignID | string | True | The ID of the campaign to send. |
For example on how to configure the CampaignSend action,
see Action examples.
Pauses a MailChimp RSS campaign.
| Parameter Name | Data Type | Required | Description |
|---|---|---|---|
| CampaignID | string | True | The ID of the campaign to pause. |
For example on how to configure the CampaignPause action,
see Action examples.
Resumes a MailChimp RSS campaign.
| Parameter Name | Data Type | Required | Description |
|---|---|---|---|
| CampaignID | string | True | The ID of the campaign to resume. |
For example on how to configure the CampaignResume action,
see Action examples.
Configure connector task dialog, click Actions.CampaignTest action, and then click Done.connectorInputPayload and then enter a value similar to the following in the
Default Value field:
{ "CampaignID": "4bd7a9abac", "TestEmails": "sample@gmail.com", "SendType": "plaintext" }
If the action is successful, the
CampaignTest task's connectorOutputPayload response
parameter will have a value similar to the following:
{ "Success": "true" }
Configure connector task dialog, click Actions.CampaignSend action, and then click Done.connectorInputPayload and then enter a value similar to the following in the
Default Value field:
{ "CampaignID": "1699382f6d" }
If the action is successful, the
CampaignSend task's connectorOutputPayload response
parameter will have a value similar to the following:
{ "Success": "true" }
Configure connector task dialog, click Actions.CampaignPause action, and then click Done.connectorInputPayload and then enter a value similar to the following in the
Default Value field:
{ "CampaignID": "4bd7a9abac" }
If the action is successful, the
CampaignPause task's connectorOutputPayload response
parameter will have a value similar to the following:
{ "Success": "true" }
Configure connector task dialog, click Actions.CampaignResume action, and then click Done.connectorInputPayload and then enter a value similar to the following in the
Default Value field:
{ "CampaignID": "4bd7a9abac" }
This example will show the specific Object records. If the action is successful, the
CampaignResume task's connectorOutputPayload response
parameter will have a value similar to the following:
{ "Success": "true" }
This section shows how to perform some of the entity operations in this connector.
Configure connector task dialog, click Entities.Entity list.List operation, and then click
Done.Configure connector task dialog, click Entities.Automations from the Entity list.Get operation, and then click
Done.1ac204985e in the Default Value field.
Here, 1ac204985e is a unique record ID in the Automations entity.
Configure connector task dialog, click Entities.Campaigns from the Entity list.Delete operation, and then click
Done.06f20ace93 in the Default Value field.
Configure connector task dialog, click Entities.CampaignFolders from the Entity list.Create operation, and then click Done.connectorInputPayload and then enter a value similar to the following in the
Default Value field:
{ "Name": "CampaignFolderCreated1707812599459" }Running this example, returns a response similar to the following in the connector task's
connectorOutputPayloadoutput variable:{ "Id": "650469bb07" }
Configure connector task dialog, click Entities.FileManagerFolders from the Entity list.Update operation, and then click Done.connectorInputPayload and then enter a value similar to the following in the
Default Value field:
{ "Name": "MyNewFolder9" }
18159 in the Default Value field.
Running this example, returns a response similar to the following in the connector
task's connectorOutputPayload output variable:
{ "Id": "18159" }
You can use the Terraform resource to create a new connection.
To learn how to apply or remove a Terraform configuration, see Basic Terraform commands.
To view a sample terraform template for connection creation, see sample template.
When creating this connection by using Terraform, you must set the following variables in your Terraform configuration file:
| Parameter name | Data type | Required | Description |
|---|---|---|---|
| datacenter | ENUM | False | The datacenter used for your MailChimp account. Supported values are: None, US1, US2, US3, US4, US5, US6, US7, US8, US9, US10, US11, US12, US13 |
| proxy_enabled | BOOLEAN | False | Select this checkbox to configure a proxy server for the connection. |
| proxy_auth_scheme | ENUM | False | The authentication type to use to authenticate to the ProxyServer proxy. Supported values are: BASIC, DIGEST, NONE |
| proxy_user | STRING | False | A user name to be used to authenticate to the ProxyServer proxy. |
| proxy_password | SECRET | False | A password to be used to authenticate to the ProxyServer proxy. |
| proxy_ssltype | ENUM | False | The SSL type to use when connecting to the ProxyServer proxy. Supported values are: AUTO, ALWAYS, NEVER, TUNNEL |
After you create the connection, it becomes available in both Apigee Integration and Application Integration. You can use the connection in an integration through the Connectors task.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-06-09 UTC.