FlowmageDocs
Mailchimp Transactional

Block an address

BetaChanges data

Puts an address on the denylist, or on the always-deliver list.

Settings

SettingWhat it is
ConnectionRequiredThe Mailchimp Transactional connection the step signs in with.
Which list"denylist" or "allowlist"
AddressRequiredtext
NoteStored with the entry so a colleague can see why it is there.
Subaccount idBlocks the address for one subaccount only. The allowlist takes none.
Technical details
KeyValue
connectiontexta connection id from `requires.connections` (provider `mailchimp-transactional`)
list"denylist" or "allowlist", by default "denylist"
emailtext
commenttext
subaccounttextused when `list` is "denylist"

Output

FieldType
entryWhat Mailchimp storedobject
emailAddressstring
addedIt was not on the list yetboolean
Sample output, and the expression for each field
  • addedtrue
  • email"gone@example.com"
  • entry
    • addedtrue
    • email"gone@example.com"

Errors

When a step of this node stops a run, the run page shows a code. Look it up:

Mailchimp Transactional errors

21 codes

Common errors

93 codes

Example step

The step as a flow file holds it. Replace each value in <…>.

{
  "config": {
    "comment": "",
    "connection": "<connection id>",
    "email": "<address>",
    "list": "denylist",
    "subaccount": ""
  },
  "label": "Block an address",
  "type": "mandrill.addSuppression",
  "version": 1
}