Eventbrite Attendee Registration Sync

Overview

FlowLibs - Eventbrite Attendee Registration Sync keeps an organization's Eventbrite registrations in sync with Dataverse and sends each new registrant a branded confirmation email. On a daily schedule it lists the organization's live Eventbrite events, pulls the attending registrants for each, and idempotently upserts them into a Dataverse table - creating a registration row and sending an Outlook confirmation the first time it sees an attendee, and quietly refreshing the existing row on subsequent runs (no duplicates, no repeat emails).

Why it matters: Eventbrite handles ticketing but not the surrounding CRM capture and branded follow-up. Wiring it to Dataverse and Outlook turns each registration into a tracked contact record and a confirmed, on-brand attendee experience, with the idempotency ledger making the sync safe to run as often as you like.

This is a demo/reference flow shipped Off. Going live requires only authorizing the three connections and setting the environment-variable values.

Use Case

A marketing/operations team uses Eventbrite for event registration and wants every attendee captured in Dataverse, a branded confirmation sent automatically, and a durable record to drive follow-up campaigns and attendance reporting.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Eventbrite	shared_eventbrite	GetOrganizationEvents
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord 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.

Sync cadence

Change the Recurrence frequency (e.g. hourly) for near-real-time capture; the idempotency ledger keeps it duplicate-safe.

Event scope

Set flowlibs_EventbriteEventStatus to started, ended, or all to widen which events are pulled.

Confirmation copy

Edit the confirmation intro variable or the Send_Confirmation_Email body to rebrand; add an ICS calendar attachment if desired.

Reminder / no-show branches

Extend with a second scheduled flow that reads flowlibs_registeredon to send day-before reminders and flag non-attendees.

Tiered comms

Branch the email by flowlibs_ticketclass (e.g. VIP vs general admission).

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.

@coalesce(body('List_Live_Events')?['events'], json('[]'))

@coalesce(body('Get_Event_Attendees')?['attendees'], json('[]'))

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

@equals(length(coalesce(body('Check_Existing_Registration')?['value'], json('[]'))), 0)

@first(body('Check_Existing_Registration')?['value'])?['flowlibs_ebattendeeregistrationid']

@coalesce(items('Apply_to_each_Attendee')?['profile']?['email'],'')

@{concat(variables('varApiBase'),'/v3/events/',items('Apply_to_each_Event')?['id'],'/attendees/?status=attending')}

Customize & download