The moment it happens
Post each Eventbrite order to Slack
Your Slack channel shows the buyer, ticket count and amount whenever an order is placed.
- Runs
- The moment it happens
- Apps
- Eventbrite
- AI
- Not needed
- Access
- private token (own org)
Send this to your assistant
Create a ClickRuntime automation: when someone places an Eventbrite order, post the buyer's name, number of tickets and order total to #event-sales in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
For small event teams, a ticket sale is a good moment to react: a large group booking may want an invoice, a VIP buyer may need a call, and a first sale on a new event tells you the launch email worked. Eventbrite sends the buyer a confirmation, but the organizer sees the order only on the dashboard or in a daily summary, long after the moment has passed.
When Eventbrite fires its order webhook, ClickRuntime receives it immediately, fetches the full order through the link in the webhook, and posts a summary to Slack with the event, the buyer, the quantity and the total. No polling delay is involved.
Teams who sell limited seating, such as supper clubs and workshops, tend to keep it in a channel that the whole crew can watch.
What you get out of it
Celebrate the first sale together
A message in the channel when a new event gets its first order gives the team a shared signal that the launch worked. It keeps morale up during the quiet stretch after tickets go live.
Spot large group bookings fast
An order for twelve tickets stands out in a feed of ones and twos. The organizer can reach out the same day about seating, invoices or a group discount, instead of discovering it a week later.
Notice odd or suspicious purchases
A burst of orders from one email or an unusually large quantity is visible as it happens. You can check for resale or fraud before the tickets are used rather than at the door.
Answer 'did my order go through?' calls
When a buyer phones to ask, anyone on the team can search the channel for the name and confirm the order. This saves a trip into the Eventbrite dashboard during a busy shift.
Keep sales visible during a launch
On launch day, watching orders land one by one tells you whether to send a reminder email or relax. Waiting for a nightly report would hide the pace of sales until the evening. That feedback loop costs nothing once running.
How it works
What happens, step by step
When someone places an order on Eventbrite, Eventbrite tells ClickRuntime straight away.
ClickRuntime looks up the order to get the buyer's name, the event, the number of tickets and the amount paid.
A message appears in your #event-sales Slack channel, such as "Jordan Lee bought 2 tickets for Northwind Product Summit: $158.00".
Before it runs live
- Connect Eventbrite
- Paste your automation's link into the other app's webhook settings
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_event, credentials, http, notify
@on_event
def handle(event):
body = event.json or {}
if body.get("config", {}).get("action") != "order.placed":
return {"skipped": True}
token = credentials.secret("EVENTBRITE_TOKEN")
order = http.get(body["api_url"], headers={"Authorization": f"Bearer {token}"},
params={"expand": "attendees,event"}).json()
tickets = len(order.get("attendees", []))
notify.slack(f"π {order['name']} bought {tickets} ticket(s) for {order['event']['name']['text']}: "
f"{order['costs']['gross']['display']}", channel="#event-sales")
return {"order": order["id"], "tickets": tickets}FAQ
Common questions
Does the alert fire for refunds and cancellations?
What information does the Slack message include?
Can I get alerts for only one event?
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
Get yesterday's ticket sales every morning
An 8am email breaks down tickets sold and revenue per live event, with totals.
See how it worksGet warned before a ticket type sells out
You hear once when any ticket class passes 90% of its capacity.
See how it worksPost new orders and sign-ups to Slack
When something happens in your shop, app or form, the details land in the right channel straight away.
See how it worksKeep exploring
Set up βPost each Eventbrite order to Slackβ from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.