Skip to content

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.

Paste it into your assistant. It tells you what it will send or change before it runs live.

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

  1. Every hour, ClickRuntime checks each ticket type on your live Eventbrite events.

  2. It compares how many tickets have sold with the total available.

  3. When a ticket type passes 90% sold, you get an email such as "Early Bird: 183/200 sold (92%)".

  4. 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

RunsHourly
Get warned before a ticket type sells outtoday, 9:00Succeeded
Email · Tickets almost sold outNorthwind Product Summit · Early Bird: 183/200 sold (92%)

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • 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

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
sell_out_capacity_alert.pyexample
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?
No. You can pick another level such as 75 or 95 percent, or set several, for example 50 and 90, so each triggers its own single alert. The comparison is made on tickets sold against total quantity. Each event keeps its own record of what was reported.
How are multiple ticket types handled?
The check looks at each ticket class and can also total across classes. You can be alerted when any single class, such as early bird or VIP, reaches the threshold, or only when the whole event does.
Will it keep alerting after the event sells out?
No. Once the event passes its last threshold and the alert is sent, it stays quiet for that event. Past events drop out of the live list, so nothing is sent after they end. If you raise capacity later, the thresholds can be reported again.
What permissions does it need?
read. Nothing else in your accounts is used.
Does it need AI?
No. It runs without AI, so it doesn't use your plan's AI allowance.
How many runs does it use?
One run each time it checks. Checks that find nothing new and stop right away aren't counted.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

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.