Use outgoing webhooks when you want HeySummit to send event-action data to another system, such as your own app, CRM, automation tool, or reporting workflow.
What a webhook does
A webhook sends data out of HeySummit when a selected action happens. Instead of another system repeatedly checking HeySummit for updates, HeySummit creates a JSON POST request to the URL you configure.
Dashboard event webhooks
Go to Event Settings > Integrations & Developer > API, MCP & Webhooks in your event dashboard.
In the Outgoing Webhooks section, select Add Webhook.
Choose the action that should trigger the webhook.
Enter the destination URL that should receive the POST request.
Leave Active? enabled if the webhook should start sending requests.
Select Add Webhook.
The destination URL must be able to receive HTTPS POST requests and should return a 200 status code when it receives the payload successfully. Dashboard event webhooks belong to one event. You need permission to change that event and the Outgoing Webhooks feature on its plan.
Dashboard webhook actions
Attendee registered: sent when an attendee completes registration.
Talk added to attendee schedule: sent when a talk is added to an attendee’s schedule.
Checkout complete: sent when an attendee completes checkout.
Speaker added to event: sent when a new speaker is added to the event.
Attendee registration started: sent when an attendee starts the registration flow.
Ticket purchase cancelled: sent when access is cancelled after an eligible refund, or when a recurring purchase is scheduled to stop at the end of its billing period.
Ticket purchase refunded: sent after a ticket, whole-order or recurring-payment refund succeeds through HeySummit.
Attendee pre-registered: sent when someone submits the event’s pre-registration form.
Talk submission submitted: sent when someone submits a talk proposal.
Refunds made directly in Stripe or another payment provider are not observed by HeySummit, so they do not trigger these dashboard webhook actions. Process the refund in HeySummit when your other systems need the webhook notification.
API-created webhook subscriptions
If you are building an account-level integration, you can also create webhook subscriptions through the HeySummit API with POST /api/v2/webhooks/. API-created subscriptions require an active paid account and your existing unrestricted API token or compatible account-level connection. Restricted API keys are limited to API v2 event endpoints and MCP. API-created subscriptions are separate from dashboard event webhooks. Creating one does not create the other. For authentication, request schemas, and supported operations, use the HeySummit API v2 documentation. API-created subscriptions can use supported event keys such as attendee.registered, attendee.registered_for_talk, attendee.communication_preferences.updated, purchaseorder.paid, and talk_submission.submitted. Use attendee.communication_preferences.updated when your integration needs to keep attendee email preference changes in sync after an attendee updates subscription settings or unsubscribes.
Payloads and delivery
HeySummit sends the payload to your configured destination. The named webhook entries in the API documentation describe payloads HeySummit sends to your destination; they are not endpoints your application should call. You can create more than one webhook or subscription, so different actions can go to different systems, or the same action can be sent to more than one destination.
Related guide
To connect a compatible AI assistant so it can read event data and preview or apply supported changes, see Connect an AI Assistant to HeySummit with MCP.