Eventbrite Sponsor Lead Capture and Sharing

Overview

This flow delivers sponsor ROI from Eventbrite events. On a schedule it scans the organization's completed events, compiles the attendees who opted in to sponsor contact (via a registration question), records each as a Dataverse Sponsor Lead, writes a compliance Sponsor Share Log entry, and emails each sponsor their qualified lead list plus a secure SharePoint link.

Why it matters: Sponsors pay for leads; delivering them promptly and compliantly is normally a manual scramble. This automates consent-based lead sharing with a full audit trail, making sponsorship measurable and repeatable.

Built as an Off demo (FlowLibs reference flow). Going live requires only authorizing the three connections and setting the environment variable values - no logic changes. Flow Checker: 0 errors / 0 warnings.

Use Case

An events team with paying sponsors wants opted-in attendee leads compiled and shared with each sponsor automatically after each event, with a defensible consent/compliance record.

Flow Architecture

Environment Variables

Connectors & Connections

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

Opt-in by ticket type instead of a question

Swap the Filter_OptIn_Attendees where to test item()?['ticket_class_name'] against an env var.

Per-sponsor routing

Replace the single sponsor env vars with a JSON SponsorMap (sponsor -> consent field + email) and look up the recipient per attendee/ticket.

Attach a real lead file

Generate an Excel/PDF of the leads and attach it (or upload to SharePoint and share an expiring link) instead of the static link.

Pagination

The attendee HTTP read takes the first page; loop on pagination.has_more_items / continuation for large events.

Schedule

Change the Recurrence frequency to match your post-event cadence.

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(string(item()?['answers'])), toLower(variables('varOptInQuestion'))), or(contains(toLower(string(item()?['answers'])), 'yes'), contains(toLower(string(item()?['answers'])), 'true')))

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

@coalesce(items('Foreach_Event')?['name']?['text'], items('Foreach_Event')?['name'], '')

@length(body('Filter_OptIn_Attendees'))

replace(replace(replace(string(body('Select_Lead_Rows')),'"},{"html":"',''),'[{"html":"',''),'"}]','')

Customize & download