Mailchimp Unsubscribe and Bounce Writeback to CRM

Overview

This flow keeps a CRM's email-consent state accurate by mirroring Mailchimp suppression events into Dataverse. On a schedule it reads the Mailchimp audience, finds members who have unsubscribed (status unsubscribed) or hard-bounced / been cleaned (status cleaned), writes those members' consent and contactability state onto a CRM contact record, appends an immutable audit-log row for each event, and posts a Teams alert to the marketing channel when hard bounces spike past a configurable threshold.

Why it matters: Emailing unsubscribed or invalid addresses is a compliance and deliverability risk. Mirroring Mailchimp opt-outs and bounces back into the CRM keeps consent state correct everywhere, automatically.

As-built note (connector-first): The Mailchimp connector has no unsubscribe / bounce / complaint trigger (its only triggers are OnMemberSubscribed and OnCreateList). The original idea described a webhook; per the connector-first rule this build uses the supported pattern instead — a built-in Recurrence trigger plus GetListMembers, detecting consent changes from each member's status field. Going live requires only authorizing the three connections and setting the environment variable values.

Use Case

Marketing and operations teams want Mailchimp opt-outs and bounces reflected on the matching CRM contact immediately and automatically, with an audit trail for compliance and a heads-up when deliverability suddenly degrades (a hard-bounce spike often signals a bad import or a domain/reputation problem).

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Mailchimp	shared_mailchimp	GetListMembers
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord UpdateRecord
Microsoft Teams	shared_teams	PostMessageToConversation

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Cadence

Change the Recurrence frequency/interval to poll more or less often (hourly by default).

Spike threshold

Edit varBounceSpikeThreshold to tune when the Teams alert fires.

Resubscribe handling

Add a branch that re-enables contactability when a member returns to subscribed.

Soft vs hard

Mailchimp cleaned is hard/undeliverable; extend the filter and event mapping if you import soft-bounce data from the Reports API.

Map to a real CRM contact

Point Find_Existing_Contact/Update_Existing_Contact at your production contact table and consent columns instead of the demo flowlibs_crmcontactconsent table.

Sunset policy

Retire chronically-bouncing addresses by querying the Consent Event Log for repeat Hard Bounce rows.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@or(equals(item()?['status'],'unsubscribed'),equals(item()?['status'],'cleaned'))

@if(equals(items('Apply_to_each_Suppressed_Member')?['status'],'cleaned'),'Hard Bounce','Unsubscribe')

@concat('flowlibs_name eq ''', items('Apply_to_each_Suppressed_Member')?['email_address'], '''')

@greater(length(outputs('Find_Existing_Contact')?['body/value']),0)

@first(outputs('Find_Existing_Contact')?['body/value'])?['flowlibs_crmcontactconsentid']

@trim(concat(coalesce(items('Apply_to_each_Suppressed_Member')?['merge_fields']?['FNAME'],''),' ',coalesce(items('Apply_to_each_Suppressed_Member')?['merge_fields']?['LNAME'],'')))

@equals(items('Apply_to_each_Suppressed_Member')?['status'],'cleaned')

@greaterOrEquals(variables('varHardBounceCount'),variables('varBounceSpikeThreshold'))

Customize & download