Mailchimp Audience Sync from Dataverse

Overview

This solution keeps a Mailchimp audience continuously aligned with marketing-consent state held in Dataverse. It ships as two cloud flows + one Dataverse table in a single solution: a real-time sync that upserts or unsubscribes a contact when its consent/details change in Dataverse, and a daily reconciliation that re-reads and re-syncs the whole contact set and emails a summary to marketing ops.

Why it matters: marketing runs in Mailchimp, but the customer record and consent live in Dataverse. Keeping them in sync prevents emailing opted-out contacts (a compliance risk) and stops the audience drifting stale. The flows ship Off; going live requires only authorizing the three connections and setting the environment-variable values.

Connector accuracy: the build uses the real shared_mailchimp ops verified against the live swagger - AddMembers (batch upsert, body/members) for subscribing and updatemember (PATCH, member identified by plain email, connector computes the MD5 subscriber hash) for unsubscribing. No HTTP fallback and no in-flow hashing.

Use Case

A marketing team runs campaigns in Mailchimp but manages contacts and consent in Dataverse (synced from a Power App, a web form, or a CRM). They want the Mailchimp audience to mirror the CRM automatically, honoring opt-outs the moment they happen and reconciling nightly as a safety net.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Mailchimp	shared_mailchimp	AddMembers updatemember
Microsoft Dataverse	shared_commondataserviceforapps	SubscribeWebhookTrigger ListRecords UpdateRecord
Office 365 Outlook	shared_office365	SendEmailV2

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.

Segmentation tags / merge fields

flowlibs_segmenttag is carried for future use; map it to a Mailchimp tag or merge field. Define custom merge fields (COMPANY, SEGMENT) in the audience before go-live.

Double opt-in

Change the subscribe status from subscribed to pending in the AddMembers member object if your compliance model requires confirmation.

Production upsert hardening

AddMembers adds new members; to bulk-update existing members' merge fields, enable Mailchimp update_existing or route updates through updatemember.

Reconciliation cadence

Adjust the Recurrence trigger (e.g. hourly) or scope List Marketing Contacts with a $filter on modifiedon for large audiences.

Bounce/unsubscribe write-back

Add a companion flow consuming Mailchimp's OnMemberSubscribed (or a webhook) to write Mailchimp-side opt-outs/bounces back into Dataverse.

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.

@equals(triggerOutputs()?['body/flowlibs_marketingconsent'], true)

@triggerOutputs()?['body/flowlibs_email']

@triggerOutputs()?['body/flowlibs_marketingcontactid']

@equals(item()?['flowlibs_marketingconsent'], true)

@not(equals(item()?['flowlibs_marketingconsent'], true))

@length(body('Filter_Opted_In_Contacts'))

Customize & download