Appearance
Mailchimp
Manage audiences, campaigns, and automations in Mailchimp.
| Detail | Value |
|---|---|
| Category | Communication |
| Base URL | https://server.api.mailchimp.com/3.0 |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | mailchimp |
Using Mailchimp in a workflow
- Go to Connections and click New Connection.
- Pick Mailchimp from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /lists | Get all audiences/lists |
GET /lists/{list_id}/members | List members of an audience |
POST /lists/{list_id}/members | Add a member to an audience |
GET /campaigns | List campaigns |
POST /campaigns | Create a campaign |
POST /campaigns/{campaign_id}/actions/send | Send a campaign |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /lists
Get all audiences/lists
| Detail | Value |
|---|---|
| Operation ID | email.listAudiences |
| Method | GET |
| Path | /lists |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
count | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mailchimp connection from the Connection dropdown.
- In the Operation dropdown, select
email.listAudiences. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mailchimp API reference.
GET /lists/{list_id}/members
List members of an audience
| Detail | Value |
|---|---|
| Operation ID | email.listMembers |
| Method | GET |
| Path | /lists/{list_id}/members |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
list_id | path | string | Yes |
count | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mailchimp connection from the Connection dropdown.
- In the Operation dropdown, select
email.listMembers. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mailchimp API reference.
POST /lists/{list_id}/members
Add a member to an audience
| Detail | Value |
|---|---|
| Operation ID | email.addMember |
| Method | POST |
| Path | /lists/{list_id}/members |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
list_id | path | string | Yes |
Request Body
| Field | Type |
|---|---|
email_address | string |
status | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mailchimp connection from the Connection dropdown.
- In the Operation dropdown, select
email.addMember. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mailchimp API reference.
GET /campaigns
List campaigns
| Detail | Value |
|---|---|
| Operation ID | email.listCampaigns |
| Method | GET |
| Path | /campaigns |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
count | query | integer | No |
status | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mailchimp connection from the Connection dropdown.
- In the Operation dropdown, select
email.listCampaigns. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mailchimp API reference.
POST /campaigns
Create a campaign
| Detail | Value |
|---|---|
| Operation ID | email.createCampaign |
| Method | POST |
| Path | /campaigns |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
type | string |
recipients | object |
settings | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mailchimp connection from the Connection dropdown.
- In the Operation dropdown, select
email.createCampaign. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mailchimp API reference.
POST /campaigns/{campaign_id}/actions/send
Send a campaign
| Detail | Value |
|---|---|
| Operation ID | email.sendCampaign |
| Method | POST |
| Path | /campaigns/{campaign_id}/actions/send |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
campaign_id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mailchimp connection from the Connection dropdown.
- In the Operation dropdown, select
email.sendCampaign. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mailchimp API reference.