Hourly
Get warned before a ticket type sells out
You hear once when any ticket class passes 90% of its capacity.
- Runs
- Hourly
- Apps
- Eventbrite
- AI
- Not needed
- Access
- read
Send this to your assistant
Create a ClickRuntime automation: check my Eventbrite events every hour and email me when a ticket class passes 90% sold, only once per ticket class.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
When an Eventbrite event is close to full, the organizer's options narrow quickly. A venue that holds 200 people at 90 percent sold leaves twenty seats, and there is still time to open a second date, release a waitlist, or tell the press that it is nearly sold out. Nobody checks capacity by hand every hour, so the moment tends to pass unnoticed until the page flips to Sold Out.
Every hour, ClickRuntime lists your events with their ticket classes, compares tickets sold with total quantity for each, and sends an alert when an event crosses 90 percent. It remembers which threshold it has already reported, so you get one message for each event rather than a repeat every hour.
It is helpful for small venues, workshops with fixed seating, and festivals with separate ticket tiers where one class can sell out first.
What you get out of it
Use the scarcity while it sells
An alert at 90 percent is the moment a nearly sold out post performs best. You can announce the last seats right away and convert hesitant buyers before the event is full.
Add capacity with time to spare
If demand is clearly outrunning the room, you can open a second session or move to a bigger venue. Learning this at 90 percent leaves weeks for logistics instead of hours.
Release held seats on purpose
Comp tickets and sponsor holds can be released or reassigned once you know the event is nearly full. That turns unused allocations into revenue instead of empty chairs on the night.
Prepare staff and supplies
Final headcount drives catering, security and staffing orders. Knowing early that a sell-out is likely lets you confirm numbers with vendors before the lead time runs out. Late changes to catering numbers are expensive and sometimes impossible.
Stop duplicate warnings
Because each threshold fires once per event, a crowded week does not bury you in repeat alerts. When a message arrives it is new information you can act on. That keeps the alert worth trusting over a long season.
How it works
What happens, step by step
Every hour, ClickRuntime checks each ticket type on your live Eventbrite events.
It compares how many tickets have sold with the total available.
When a ticket type passes 90% sold, you get an email such as "Early Bird: 183/200 sold (92%)".
Each ticket type is reported only once, so you are not warned again on the next check.
Before it runs live
- Connect Eventbrite
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Eventbrite steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, credentials, http, state, notify, report_fetched
ORG_ID = "your-organization-id"
API = "https://www.eventbriteapi.com/v3"
@on_trigger
def run(event):
h = {"Authorization": f"Bearer {credentials.secret('EVENTBRITE_TOKEN')}"}
alerted = set(state.get("alerted") or [])
events = http.get(f"{API}/organizations/{ORG_ID}/events/", headers=h, params={"status": "live"}).json()["events"]
hits = []
for ev in events:
for tc in http.get(f"{API}/events/{ev['id']}/ticket_classes/", headers=h).json()["ticket_classes"]:
total = tc.get("quantity_total") or 0
if total and tc["quantity_sold"] / total >= 0.9 and tc["id"] not in alerted:
hits.append(f"{ev['name']['text']} · {tc['name']}: {tc['quantity_sold']}/{total} sold")
alerted.add(tc["id"])
report_fetched(len(hits))
if not hits:
return {"alerts": 0}
notify.email_me("Tickets almost sold out", "\n".join(hits))
state.set("alerted", sorted(alerted))
return {"alerts": len(hits)}FAQ
Common questions
Is the 90% threshold fixed?
How are multiple ticket types handled?
Will it keep alerting after the event sells out?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Post each Eventbrite order to Slack
Your Slack channel shows the buyer, ticket count and amount whenever an order is placed.
See how it worksGet yesterday's ticket sales every morning
An 8am email breaks down tickets sold and revenue per live event, with totals.
See how it worksSee new job listings as they're posted
Jobs that match your keywords show up in a Slack channel, each one only once.
See how it worksKeep exploring
Set up “Get warned before a ticket type sells out” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.