Eventbrite Live Check-In Dashboard
As attendees check in at an Eventbrite event, the flow updates a live attendance count in Dataverse, posts milestone alerts (25/50/75/100% of registered) to a Teams event channel, and flags no-shows after the start time. Gives organizers a real-time view of turnout without watching the Eventbrite app.
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 gives event organizers a real-time turnout view for live Eventbrite events without watching the Eventbrite app. On a 15-minute schedule it lists the organization's live events, reads each event's attendee check-in state, upserts a live attendance stat row in Dataverse, and posts 25/50/75/100% turnout milestone alerts to a Teams event channel. It also records no-shows (registered minus checked-in) once an event's start time has passed.
Why it matters: Live milestones and no-show counts surfaced in Teams keep the whole events team informed and able to react (e.g. release a waitlist) without anyone babysitting the Eventbrite dashboard.
Status: Built and deployed to the environment as a solution-aware cloud flow. Ships Off (demo). Going live requires only connection authorization + env var configuration (see Customization Guide).
Use Case
An events team running in-person events wants live check-in visibility and no-show detection surfaced in a Teams channel, with a durable Dataverse record of turnout per event for reporting.
Flow Architecture
Recurrence
Recurrence (every 15 min)Polls Eventbrite on a schedule
Initialize variables
Initialize variableEventbrite org id, REST base URL, private token, Teams group/channel ids, and milestone band size
Get Live Events
Eventbrite GetOrganizationEventsLists the org's live events (connector-first data source)
Apply to each Event
Foreach (concurrency 1)Processes each live event: read attendees, count checked-in, compute pct/band/no-shows, upsert stat row, alert on new milestone
Get Attendees
HTTP GET (documented fallback)Reads the event's attendees incl. checked_in
Condition Stat Exists
If (upsert) -> Dataverse UpdateRecord / CreateRecordUpdate stat row if it exists, else create it; writes latest counts + current band
Condition Milestone
If -> Teams PostMessageToConversationFires only when a new, higher band is crossed; posts the turnout milestone alert
Environment Variables
| Schema name | Type | Default | Description |
|---|---|---|---|
| flowlibs_EventbriteOrgId | String | (org id) | Eventbrite organization id for GetOrganizationEvents |
| flowlibs_EventbriteApiBase | String | https://www.eventbriteapi.com | Base URL for the attendees REST call |
| flowlibs_EventbriteApiToken | String | (private token) | Bearer token for the attendees REST call |
| flowlibs_TeamsGroupId | String | <your-team-id> | Teams team (group) id of the event channel |
| flowlibs_TeamsChannelId | String | <your-channel-id> | Teams channel id for milestone alerts |
| flowlibs_CheckInMilestoneBand | String | 25 | Milestone band size (25 = alert at 25/50/75/100%) - new this build |
Connectors & Connections
| Connector | API name | Actions used |
|---|---|---|
| Eventbrite | shared_eventbrite | GetOrganizationEvents |
| Microsoft Teams | shared_teams | PostMessageToConversation |
| Microsoft Dataverse | shared_commondataserviceforapps | ListRecords CreateRecord UpdateRecord |
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.
- Set the env vars
- Before turning on: Eventbrite org id + private token, the Teams group/channel ids of your event channel, and the milestone band size (default 25 -> alerts at 25/50/75/100%; set 20 for finer bands).
- Authorize connections
- Authorize the three connections (Eventbrite, Teams, Dataverse) on first open.
- Polling cadence
- Change the Recurrence interval (default 15 min) for closer-to-real-time updates.
- Attendee pagination
- The Eventbrite attendees endpoint returns the first page (50). For very large events, extend Get Attendees to follow pagination.has_more_items / continuation and accumulate the checked-in count across pages.
- Per-session tracking
- For multi-track events, key the stat row on event id + session/track to track check-ins per session.
- Live artifact / Power BI
- Point a Power BI report or a live view at the flowlibs_eventcheckinstat table for a visual dashboard.
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.01Check-in %
Whole-number check-in percentage
EXPR.02Milestone band
Current milestone band
EXPR.03No-shows (after start only)
Registered minus checked-in, only after event start
EXPR.04New-milestone test
Fires exactly one alert when crossing into a higher band
EXPR.05Existing-row lookup ($filter)
Dataverse ListRecords filter by event id
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.