Skip to main content

How to Set Up Webhooks for Event Actions

Jerica avatar
Written by Jerica
Updated today

Webhooks allow you to send notifications about specific actions in an event, providing real-time data to external platforms when certain triggers occur.

What is a Webhook?

A webhook is a way for HeySummit to send data to an external platform. Unlike an API, which pulls data into HeySummit, a webhook pushes data out. When a specific action happens in your event, such as a registration or completed checkout, a webhook sends that data immediately to an external URL.

Setting Up a Webhook

  1. Access the Webhook Settings:

    • In HeySummit, go to Setup > Webhooks and click on Add Webhook.

  2. Activate the Webhook:

    • After adding a webhook, you can toggle it on or off. When activated, the webhook will send notifications based on your specified triggers.

  3. Select the Trigger:

    • Choose one of the available actions to trigger the webhook. These currently include:

      • Registration Started: Triggered when an attendee starts their registration (usually when they enter their email).

      • Checkout Complete: Triggered when an attendee completes the registration checkout.

      • Talk Added to Schedule: Triggered when a talk is added to an attendee’s schedule.

  4. Enter the URL:

    • Enter the URL of the external platform where the data should be sent. This could be your website or another service that supports webhooks.

    • The URL must be capable of receiving POST requests, which will be used to send the data.

  5. Data Sent via Webhook:

When the trigger event happens, a POST request will be sent to the specified URL. Here's an example of what we send for each:

Attendee Registration Started:


Talk Added to Attendee Schedule:


Checkout Complete:


The external platform receiving the data must return a 200 status code to confirm that the data was successfully received.

Multiple Webhooks:

  • You can create multiple webhooks for different actions or send the same data to multiple destinations. For example, you could set up separate webhooks to notify different systems when an attendee registers or completes checkout.

If you need to add more triggers or receive additional data, let us know, and we can update the available options for webhooks.

Did this answer your question?