MailchimpSet contact tags
BetaChanges data
Sets which tags a contact carries, creating a tag Mailchimp does not know yet.
Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Mailchimp connection the step signs in with. |
| Audience id | Picked from the list Mailchimp offers. |
| E-mail address | text |
| Tags | One row per tag. Active adds it, Inactive takes it off. A tag Mailchimp does not know yet is created when you set it active. |
| Tags from an earlier node | The rows above are literal text. Use this instead when the tag names come from an earlier node; it replaces them. |
| Do not fire automations | Mailchimp's own automations that watch these tags will not fire. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `mailchimp`) |
audienceId | texta value from the vendor's own list |
email | text |
tags | list of {name?: text, status?: "active" or "inactive"}, by default [] |
tagsJson | list of any JSON, by default [] |
isSyncing | true/false, by default false |
Output
| Field | Type |
|---|---|
taggedTags were set | boolean |
tagCountTags in this call | number |
emailE-mail address | string |
Sample output, and the expression for each field
- email"person@example.com"
- tagCount2
- taggedtrue
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": "",
"connection": "<connection id>",
"email": "",
"isSyncing": false,
"tags": [],
"tagsJson": []
},
"label": "Set contact tags",
"type": "mailchimp.setMemberTags",
"version": 1
}