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 Setup > 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 Save.
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 and require the Outgoing Webhooks feature to be available on your plan.
Dashboard webhook actions
Attendee registration started: sent when an attendee enters the registration flow.
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.
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 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.