Skip to content
For LLMsView as Markdown·

Mailchimp

Manage audiences, campaigns, and automations in Mailchimp.

DetailValue
CategoryCommunication
Base URLhttps://server.api.mailchimp.com/3.0
AuthenticationBearer Token
Endpoints6
Connector keymailchimp

Using Mailchimp in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Mailchimp from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
GET /listsGet all audiences/lists
GET /lists/{list_id}/membersList members of an audience
POST /lists/{list_id}/membersAdd a member to an audience
GET /campaignsList campaigns
POST /campaignsCreate a campaign
POST /campaigns/{campaign_id}/actions/sendSend 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

DetailValue
Operation IDemail.listAudiences
MethodGET
Path/lists

Parameters

NameLocationTypeRequired
countqueryintegerNo

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Mailchimp connection from the Connection dropdown.
  3. In the Operation dropdown, select email.listAudiences.
  4. 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

DetailValue
Operation IDemail.listMembers
MethodGET
Path/lists/{list_id}/members

Parameters

NameLocationTypeRequired
list_idpathstringYes
countqueryintegerNo

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Mailchimp connection from the Connection dropdown.
  3. In the Operation dropdown, select email.listMembers.
  4. 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

DetailValue
Operation IDemail.addMember
MethodPOST
Path/lists/{list_id}/members

Parameters

NameLocationTypeRequired
list_idpathstringYes

Request Body

FieldType
email_addressstring
statusstring

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Mailchimp connection from the Connection dropdown.
  3. In the Operation dropdown, select email.addMember.
  4. 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

DetailValue
Operation IDemail.listCampaigns
MethodGET
Path/campaigns

Parameters

NameLocationTypeRequired
countqueryintegerNo
statusquerystringNo

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Mailchimp connection from the Connection dropdown.
  3. In the Operation dropdown, select email.listCampaigns.
  4. 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

DetailValue
Operation IDemail.createCampaign
MethodPOST
Path/campaigns

Parameters

No parameters.

Request Body

FieldType
typestring
recipientsobject
settingsobject

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Mailchimp connection from the Connection dropdown.
  3. In the Operation dropdown, select email.createCampaign.
  4. 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

DetailValue
Operation IDemail.sendCampaign
MethodPOST
Path/campaigns/{campaign_id}/actions/send

Parameters

NameLocationTypeRequired
campaign_idpathstringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Mailchimp connection from the Connection dropdown.
  3. In the Operation dropdown, select email.sendCampaign.
  4. 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.