Mailchimp TransactionalUpdate template
BetaChanges data
Changes an existing template's subject, sender or code.
Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Mailchimp Transactional connection the step signs in with. |
| Template slugRequired | The template's immutable slug — the List templates node answers it beside the display name. |
| Default subject | text |
| Default from address | text |
| Default from name | text |
| HTML | Left empty, the template's HTML is left alone; filled in, it replaces what was there. |
| Plain text | text |
| Labels | Comma-separated, at most 10. |
| Publish the change | Off writes the draft only, so the send nodes keep using the version that is live now. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `mailchimp-transactional`) |
templateSlug | text |
subject | text |
fromEmail | text |
fromName | text |
code | text |
text | text |
labels | text |
publish | true/false, by default true |
Output
| Field | Type |
|---|---|
templateThe template as it now stands | object |
Sample output, and the expression for each field
- template
- slug"order-confirmation"
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": {
"code": "",
"connection": "<connection id>",
"fromEmail": "",
"fromName": "",
"labels": "",
"publish": true,
"subject": "",
"templateSlug": "<template slug>",
"text": ""
},
"label": "Update template",
"type": "mandrill.updateTemplate",
"version": 1
}