No event platform is the only tool a team uses. A purchase needs to reach the finance sheet, a registration needs to reach the CRM, and a check-in might need to ping the team chat. In Geiger Events, that connection is a webhook step inside an automation: when something happens at your event, Geiger Events makes an HTTP request to a URL you choose.
How a webhook automation works
Every automation is a trigger, optional conditions, and one or more steps. A webhook is one of those steps, so it composes with everything else an automation can do — send an email, send an SMS, add a tag, add a contact to a segment, update a field or create a follow-up task for your team.
- Pick a trigger. Ticket purchased, registration submitted, RSVP confirmed, refund issued, payment failed, attendee checked in, waitlist joined, event published, event starting soon, or attendee no-show.
- Narrow it with conditions (optional). Only fire for a given ticket type, for orders above an amount, for buyers with a specific attribute, or for contacts carrying a tag.
- Add a Webhook step. Choose the method — POST, GET or PUT — and the URL of the endpoint that should receive it.
- Turn it on. Automations have Draft, Active and Paused states, and every run is recorded in the automation's history, so you can see what fired and when.
What teams connect
- Sales into finance. Post every ticket purchase and refund to the endpoint that feeds your accounting sheet or data warehouse.
- Registrations into a CRM. Send each registration submitted to your CRM's inbound endpoint, or to an automation tool that maps it for you.
- Door activity into team chat. Fire a check-in webhook at a chat incoming-hook URL, filtered to VIP ticket types, so hosts know when key guests arrive.
- Payment problems into support. A payment-failed trigger can notify your helpdesk while a second step emails the buyer a nudge to retry.
Webhooks, native steps, or both
If the job stays inside Geiger Events — a reminder email, a tag, a task for a colleague — use the native step; it needs no endpoint and no code. Reach for the webhook step when the data has to leave the platform. Most useful automations mix the two: tag the buyer, email them, and post the order to your finance endpoint, all from one trigger.
What is not here yet
A public REST API for pulling events, orders and attendees on demand is on the roadmap but not available today. Until it ships, webhooks cover the "tell another system when something happens" case, and exports from your attendee CRM and registrations cover bulk data. The data your webhooks send comes from the same records as your orders, registrations and check-ins, so there is nothing to reconcile.
What changes for you
Event activity stops being something you export on Fridays. The moment a ticket sells or a guest walks in, the systems that care hear about it — with conditions so they only hear what matters. See how automations fit your plan on the pricing page.