Short answer: You can update list member in Mailchimp by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Mailchimp Update List Member action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Audience/List ID list_id | string | Required | Mailchimp audience (list) ID — a 10-char hex string. Find in Audience > Settings > Audience name & defaults. |
Subscriber Hash subscriber_hash | string | Required | Lowercase MD5 hash of the subscriber's email. Pass the email if your SDK auto-hashes. |
Status status | options | Optional | Status. Options: Subscribed, Unsubscribed, Cleaned, Pending |
First Name first_name | string | Optional | Contact's first (given) name. |
Last Name last_name | string | Optional | Contact's last (family) name. |
{"list_id": "e.g. a1b2c3d4e5","subscriber_hash": "e.g. 7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d","status": "{{trigger.status}}","first_name": "e.g. Jane","last_name": "e.g. Doe"}
{"id": "abc123","status": "subscribed","email_address": "user@example.com"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.