Archive Member
mailchimp.archive_member
ActionEmailconnection required
Calls the Mailchimp API with the connection's credentials.
Archive an audience member: it stops counting against the plan and receives nothing, but its history survives and it can be re-added.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Mailchimp
- Secret shape
- the Mailchimp API key (…-<dc>)
- Config it needs
- dc
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
list_id The audience (list) id, as shown in Mailchimp under Audience settings and returned as 'id' by Mailchimp: List Audiences. | string | Yes | — | — | — |
email The member's email address. Mailchimp addresses a member by the MD5 of the lowercased address, which this node derives for you; a 32-character subscriber hash from an earlier step is accepted as-is. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
archived True once Mailchimp accepted the archive. | boolean | — |
list_id The audience the member was archived in. | string | — |
subscriber_hash The MD5 address of the archived member. | string | — |
{
"archived": false,
"list_id": "",
"subscriber_hash": ""
}See Archive Member run in a workflow.
In a technical demo we add the Mailchimp connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.