Eventbrite Attendee to Marketing Audience Sync

Overview

A scheduled Power Automate cloud flow that pulls registrants from live Eventbrite events, syncs the ones who opted in to marketing into a Mailchimp audience (idempotent upsert with merge fields), and mirrors each synced contact to a Dataverse ledger table. The ledger doubles as the idempotency guard so each Eventbrite attendee is synced exactly once. Built API-first; ships Off.

Use Case

Marketing and Sales teams want event registrations to feed the nurture engine automatically without manual list imports. This flow turns Eventbrite registrations into Mailchimp audience members (tagged by event) and keeps a governed CRM record of who was synced - honoring marketing opt-in and avoiding duplicates.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Eventbrite	shared_eventbrite	GetOrganizationEvents
Mailchimp	shared_mailchimp	AddMembers
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord

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.

Event scope

Change the GetOrganizationEvents status (e.g. live,started,ended) to widen which events are scanned.

Opt-in detection

Point flowlibs_EventbriteOptInQuestion at your registration question text and extend the affirmative answer set in Initialize Affirmative Values.

Cadence

Adjust the Recurrence frequency/interval to your registration volume.

Mailchimp tags

The connector exposes no tags operation, so the event tag rides in the EVENTTAG merge field. Add a follow-up call to the Mailchimp tags endpoint to apply true tags.

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.

@and(contains(toLower(coalesce(item()?['question'], '')), toLower(parameters('EnvVar_OptInQuestion'))), contains(split(variables('varAffirmativeValues'), ','), toLower(trim(coalesce(item()?['answer'], '')))))

@concat('flowlibs_attendeeid eq ''', string(items('For_Each_Attendee')?['id']), '''')

@{concat(parameters('EnvVar_EventbriteApiBase'), '/v3/events/', items('For_Each_Event')?['id'], '/attendees/?status=attending&page_size=50')}

Customize & download