Eventbrite Sponsor Lead Capture and Sharing
After an Eventbrite event, the flow compiles the attendees who opted in to sponsor contact, records each as a Dataverse Sponsor Lead, writes a compliance share-log entry, and emails each sponsor their qualified lead list plus a secure SharePoint link. Delivers sponsor ROI automatically with a full consent audit trail.
Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.
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
Recurrence
Recurrence (Day/1)Runs daily to process recently completed events
Compose Correlation Id
Compose (guid)Unique run id stamped on all records
Initialize variables
Initialize Variable x8Loads the 8 environment variables into variables
Get Completed Events
Eventbrite GetOrganizationEventsLists org events matching the status filter
Foreach Event
Foreach (concurrency 1)Processes each event in turn
Get Event Attendees
HTTP GET (Eventbrite REST)Reads attendees (no connector list-attendees op)
Filter Opt-In Attendees
Filter ArrayKeeps attendees who answered the opt-in question affirmatively
Foreach Lead - Create Lead Record
Foreach + Dataverse CreateRecordWrites each opted-in attendee to flowlibs_sponsorleads
If Has Leads
IfOnly logs/emails when leads exist (skips empty events)
Build Leads Table
Select + ComposeBuilds the HTML lead table for the email
Create Share Log
Dataverse CreateRecordWrites the compliance entry to flowlibs_sponsorsharelogs
Environment Variables
| Schema name | Type | Default | Description |
|---|---|---|---|
| flowlibs_EventbriteOrgId | String | (set per tenant) | Eventbrite organization id to scan |
| flowlibs_EventbriteApiBase | String | https://www.eventbriteapi.com | Base URL for the attendee REST read |
| flowlibs_EventbriteApiToken | String | (set per tenant) | Eventbrite private token (Bearer for the attendee read) |
| flowlibs_EventbriteEventStatus | String | live | Status filter for GetOrganizationEvents; set to ended for post-event processing |
| flowlibs_EventbriteOptInQuestion | String | Can we email you marketing updates? | Registration question text that signals sponsor opt-in |
| flowlibs_SponsorEmail | String | sponsors@contoso.com | Sponsor recipient email |
| flowlibs_SponsorName | String | Contoso Sponsorships | Sponsor display name |
| flowlibs_SponsorLeadsSharePointLink | String | https://your-tenant.sharepoint.com/sites/Sponsors/Shared Documents/Leads | Secure SharePoint link included in the sponsor email |
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.
EXPR.01Opt-in filter (Query where)
Keeps affirmative opt-in answers
EXPR.02Attendee URI
Eventbrite REST attendees URL
EXPR.03Event name (v3 object)
Friendly event name with fallback
EXPR.04Lead count as native integer
Lead count for the Share Log
EXPR.05HTML table unwrap
Unwraps the Select output into clean HTML rows
Customize & download
Generate a ready-to-import copy of this solution with your environment-variable values baked in — available on Base, Pro, or Team.
Upgrade to customize
Comments
Sign in to join the conversation.
Sign inNo comments yet. Be the first to share your experience with this flow.