MailchimpAdd contact event
BetaChanges data
Writes a custom event onto a contact so a journey can branch on it.
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 |
| Event name | 2 to 30 characters. This is the name a journey's condition matches on. |
| Event properties | Mailchimp stores event properties as text. |
| Happened at | ISO 8601. Left empty, Mailchimp uses the moment it receives the event. |
| Do not fire journeys | The journeys watching this event 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 |
name | text |
properties | object of text, by default {} |
occurredAt | text |
isSyncing | true/false, by default false |
Output
| Field | Type |
|---|---|
writtenEvent written | boolean |
nameEvent name | string |
emailE-mail address | string |
Sample output, and the expression for each field
- email"person@example.com"
- name"placed_order"
- writtentrue
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,
"name": "",
"occurredAt": "",
"properties": {}
},
"label": "Add contact event",
"type": "mailchimp.addMemberEvent",
"version": 1
}