Eventbrite Daily Sales and Revenue Digest
Each morning the flow pulls Eventbrite ticket sales and revenue for active events (sold vs capacity, revenue, sales velocity, days to event) and posts a digest to a Teams marketing channel plus an email to the organizer. Flags events pacing below target. Keeps the team on top of sales without opening Eventbrite.
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 a daily readout of Eventbrite ticket sales for an organization's live events. Each morning at 8:00 AM it lists the org's live events via the Eventbrite connector, pulls per-event ticket-class sales over the Eventbrite REST API, computes sold-vs-capacity, gross revenue, sold %, days-to-event and a pacing flag, then posts an HTML digest to a Teams marketing channel and emails the organizer. Events pacing below the configurable target are counted and flagged.
Why it matters: Sales-pacing data lives in an Eventbrite dashboard nobody opens daily. A pushed digest surfaces underperforming events early enough to boost promotion.
Status: Built and verified (Flow Checker 0 errors / 0 warnings). Ships Off - going live requires only connection authorization and env-var configuration.
Use Case
A marketing / events team running multiple concurrent Eventbrite events wants a daily sales snapshot - with pacing flags - delivered where they already work (Teams + email), without logging into Eventbrite.
Flow Architecture
Daily 0800 Morning Trigger
Recurrence (Day/1, 08:00 EST)Fire the morning digest
Initialize variables
Initialize VariablePacing target, API base, HTML accumulator, underpacing counter, and per-event sold/capacity/gross/currency working vars
List Active Events
Eventbrite GetOrganizationEventsList the org's live events (order_by start_asc)
Apply to each Event
Foreach (concurrency 1)Process each event; reset accumulators, fetch ticket classes via HTTP, sum sold/capacity/gross, compute pacing, append HTML row
Get Ticket Classes
HTTP (Eventbrite REST)Per-event ticket classes (sold, capacity, price) - no connector op exists
Compose Digest Html
ComposeAssemble heading + summary + table
Post Digest to Teams
Teams PostMessageToConversationPost digest to marketing channel
Email Organizer
Outlook SendEmailV2Email the same digest to the organizer
Environment Variables
| Schema name | Type | Default | Description |
|---|---|---|---|
| flowlibs_EventbriteOrgId | String | (org id) | Eventbrite organization whose events are reported |
| flowlibs_EventbriteApiBase | String | https://www.eventbriteapi.com | Base URL for the REST ticket-class lookup |
| flowlibs_EventbriteApiToken | String | (token) | Eventbrite OAuth token for the REST ticket-class call |
| flowlibs_PacingTargetPct | String | 70 | Sold % expected by now; events below are flagged |
| flowlibs_OrganizerEmail | String | events@yourcompany.com | Digest email recipient |
| flowlibs_TeamsGroupId | String | <your-team-id> | Marketing Team group id |
| flowlibs_TeamsChannelId | String | <your-channel-id> | Marketing channel id |
Connectors & Connections
| Connector | API name | Actions used |
|---|---|---|
| Eventbrite | shared_eventbrite | GetOrganizationEvents |
| Microsoft Teams | shared_teams | PostMessageToConversation |
| 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.
- Pacing target
- Change flowlibs_PacingTargetPct (e.g. 80) without touching flow logic.
- Schedule
- Adjust the Recurrence trigger frequency / start time / time zone.
- Per-event owners
- Replace the single flowlibs_OrganizerEmail with a per-event owner lookup so each event's owner gets their own numbers.
- Power BI
- Pair with a sales-to-Dataverse/PBI sync for trend charts over time.
- Promo trigger
- Branch on the underpacing flag to auto-launch a discount or email campaign.
- Ticket-class detail
- The inner loop already has each class's sold/total/price; expose a per-class breakdown in the digest if desired.
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.01Sold % (per event)
Whole-number sold percentage per event
EXPR.02Gross revenue accrual (per ticket class)
cost.value is in minor units (cents)
EXPR.03Days to event
Days remaining until the event start
EXPR.04Underpacing flag
Status label vs pacing target
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.