
Supported Webhook Events
KonfHub can notify your endpoint for the following event types. You choose which events trigger your webhook when you configure it.Attendee Registration
Fires when a new attendee successfully completes registration for your event. Includes full attendee details and ticket information.
Attendee Cancellation
Fires when an attendee cancels their registration. Use this to update your CRM, free up reserved resources, or trigger a follow-up workflow.
Check-In
Fires when an attendee is checked in at the venue using the KonfHub Check-in App. Useful for real-time attendance tracking dashboards.
Check-Out
Fires when an attendee checks out of the venue. Helps track session attendance duration and manage capacity in multi-area events.
Lead Generation
Fires when a lead is captured for your event through the Lead Capture App. Use this to immediately push lead data into your sales pipeline.
Configuring a Webhook
1
Open Your Event Dashboard
Log in to KonfHub, select your event, and navigate to the Developers section in the left-hand sidebar.
2
Go to Webhooks
Click on Webhooks within the Developers section. You will see the webhook configuration panel.
3
Enter Your Webhook URL
Paste the URL of the endpoint on your server where KonfHub should send POST requests. Make sure the endpoint is publicly accessible and returns a
200 OK response when it receives a request.4
Select the Events to Trigger
Check the boxes next to each event type you want to receive notifications for: Attendee Registration, Attendee Cancellation, Check-In, Check-Out, and/or Lead Generation.
5
Save and Test
Save your configuration. KonfHub will begin sending POST requests to your URL immediately when the selected events occur. Use a tool like Webhook.site to test and inspect the payload before connecting to your production system.
Webhook Payload Structure
KonfHub sends webhook notifications as HTTPPOST requests with a Content-Type: application/json header. Below is an example payload for an Attendee Registration event:
Example: Attendee Cancellation
Example: Check-In
Example: Lead Generation
Example Use Cases
Webhooks are the foundation for real-time integrations between KonfHub and the rest of your event stack. Here are some common patterns:Add registrants to your CRM automatically
Add registrants to your CRM automatically
When a new
attendee.registered event arrives, parse the attendee’s name, email, and ticket type, then call your CRM’s API (e.g., HubSpot, Salesforce) to create or update a contact record. This eliminates manual CSV exports and import delays.Send custom SMS, email, or WhatsApp confirmations
Send custom SMS, email, or WhatsApp confirmations
Trigger your own messaging workflow on every
attendee.registered event. Route the payload to your SMS provider (e.g., Twilio), transactional email service (e.g., SendGrid), or WhatsApp Business API to send a branded confirmation message outside of KonfHub’s standard communications.Update a live attendance spreadsheet
Update a live attendance spreadsheet
Forward
attendee.checked_in and attendee.checked_out events to a Google Sheets or Airtable automation to maintain a live attendance log. Pair this with a dashboard for a real-time view of who is on-site.Push leads directly into your sales pipeline
Push leads directly into your sales pipeline
When a
lead.generated event fires, immediately create a deal or opportunity in your CRM and assign it to the appropriate sales representative. This ensures no lead captured at your event booth goes cold.Trigger Slack or Teams notifications
Trigger Slack or Teams notifications
Send a message to your event operations Slack channel every time a new VIP or speaker registers. Filter on ticket type in your webhook handler and only notify your team for specific registrations.
Retry Behavior and Reliability
KonfHub makes a best-effort delivery of webhook notifications. If your endpoint returns a non-200 status code or is unreachable, KonfHub will retry the request automatically a set number of times with an exponential back-off delay.
To ensure reliable delivery, design your webhook endpoint to be idempotent — processing the same payload more than once should not cause duplicate records or unintended side effects. Use the
attendee_id or lead_id fields as idempotency keys.Plan Availability
Webhooks are available on the Silver plan and above.
To upgrade your plan, visit konfhub.com/pricing or contact the KonfHub sales team.