Special workflows for Mailchimp.
Each scenario shows the trigger, the Volimox handoff, and the human checkpoint. These are concrete workflow blueprints, not a claim that every connection is live today.
Consented lead to audience
Keep permissioned customer follow-up aligned with lead status.
Starts when
A Volimox lead is qualified and has the required marketing consent.
Result
Marketing audiences stay useful without bypassing customer communication preferences.
Volimox workflow
- 01Volimox checks consent, source, and the selected audience rule.
- 02Volimox adds or updates the subscriber with the correct tag.
- 03The marketing owner can review the source lead before a campaign uses it.
Human checkpoint
No contact is added without an explicit permission signal.
Unsubscribe to team visibility
Make a Mailchimp preference change visible to the team handling the customer.
Starts when
Mailchimp reports an unsubscribe or tag change for a linked contact.
Result
Customer preference changes remain visible across operations and marketing.
Volimox workflow
- 01Volimox matches the subscriber to the customer record.
- 02Volimox updates the communication preference and preserves the source event.
- 03The owner receives an internal note when the preference affects an active workflow.
Human checkpoint
An unsubscribe never starts a new marketing or promotional message.
Supported triggers and actions.
A trigger starts the workflow. An action is the controlled operation Volimox performs after the rules pass.
Triggers
- New subscriber
- Unsubscribe
- Tag added
Actions
- Add subscriber
- Update subscriber
- Add tag
- Remove tag
Detailed connection code.
This server-side TypeScript reference follows the same connection → action → mapped input pattern used by modern automation platforms. Provider credentials remain inside the approved connection; browser code never receives them.
TypeScript · server only
Add or update a consented subscriber
import { createZapierSdk } from "@zapier/zapier-sdk"
const zapier = createZapierSdk({
apiKey: process.env.ZAPIER_API_KEY,
})
export async function runMailchimpAction() {
const { data: connection } = await zapier.findFirstConnection({
app: "mailchimp",
owner: "me",
})
if (!connection) {
throw new Error("No approved Mailchimp connection was found")
}
const result = await zapier.runAction({
app: "mailchimp",
action: "add_update_subscriber",
connection: connection.id,
input:
{
"audienceId": "{{env.MAILCHIMP_AUDIENCE_ID}}",
"email": "{{lead.email}}",
"statusIfNew": "subscribed",
"tags": "Volimox,Qualified",
"mergeFields": "FNAME={{lead.firstName}},LNAME={{lead.lastName}}"
},
})
return result.data
}Connection setup.
The setup path is specific to the provider. We will never ask you to paste credentials into a public page.
Mailchimp OAuth
A reviewable connection, step by step.
- 01Choose an audience
- 02Map consent and source fields
- 03Review marketing permissions
This app is cataloged and its workflow contract is defined. We will enable the connection after provider access and sandbox verification.
Related apps