MailchimpSettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Mailchimp connection the step signs in with. |
| Audience id | Picked from the list Mailchimp offers. |
| Segment name | text |
| Kind | "static" or "saved" |
| Addresses | Comma separated. Left empty, Mailchimp creates an empty static segment you can fill later. |
| Match | "any" or "all" |
| Conditions | Mailchimp's own condition grammar — around forty condition types, each with its own operators. The vendor's segmentation-conditions page lists them. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `mailchimp`) |
audienceId | texta value from the vendor's own list |
name | text |
kind | "static" or "saved", by default "static" |
staticMembers | textused when `kind` is "static" |
match | "any" or "all", by default "any"used when `kind` is "saved" |
conditionsJson | list of any JSON, by default []used when `kind` is "saved" |
Output
| Field | Type |
|---|---|
segment | object |
segmentId | number |
memberCountContacts in the segment | number |
Sample output, and the expression for each field
- memberCount0
- segment
- id7
- name"Customers"
- segmentId7
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"audienceId": "",
"conditionsJson": [],
"connection": "<connection id>",
"kind": "static",
"match": "any",
"name": "",
"staticMembers": ""
},
"label": "Create segment",
"type": "mailchimp.createSegment",
"version": 1
}