Webhooks

If you’re unfamiliar with webhooks, think of them as tools for automated data delivery. Instead of manually checking for updates, admins are notified as soon as new data is available. You can use webhooks to send these notifications to third-party platforms like Slack, Microsoft Teams, or Cisco.

To get started, first create a webhook in your chosen platform (e.g., Slack, Teams, etc.). Then, in your event console:

1. Go to the Tools tab and click Integrations

2. Select Webhooks

3. Click Add to set up your webhook connection

Setting Up a Webhook

After clicking Add, you’ll be asked to configure several fields to define what kind of notifications you want to receive.

Event Types and Actions: Each webhook is associated with a specific event type and a corresponding action. The action determines when the webhook should activate based on activity.

• Attendee
  Notified when an attendee is created, updated, or deleted.

• Meeting
  Notified when a meeting is booked, rescheduled, cancelled, or when an attendee’s status is updated.

• Session
  Notified when a session is created, booked, unbooked, joined, or watched.

• Sponsor
  Notified on sponsor-related activities such as product creation, deletion, update, view, link click, asset download, chat, or when marked as interested.

• Poll
  Notified when a poll is created or answered.

Example:
Event Type: Meeting
Action: Book
You’ll receive a notification whenever a meeting is booked.

Content Type:

• application/json – Sends data in JSON format
• application/x-www-form-urlencoded – Sends data in a single block in the HTTP message body
  

Status:

• Set the webhook to Active or Inactive

Endpoint: 

• Enter the URL of the destination (e.g., Slack, Teams) where you want the webhook to send data.

Headers: When your webhook sends data, you can tack on extra pieces of information called headers. These help the receiving system know who’s sending data, verify it’s genuine, or pass along small bits of “behind-the-scenes” info.

• Key: The name of the header (label); Tells the server what kind of information this is
• Value: The content that goes with that name; The actual data or token you want to send

How to use:

1. In Key, type the header name
   • Examples:
     • Authorization
     • X-Client-ID
     • X-Signature
2. In Value, type what you need to send
   • Examples:
     • Bearer abcd1234 (your secret token)
     • 67890 (your app’s ID)
     • f1e2d3c4b5 (a checksum or signature)

Now, every time the webhook runs, it will include those named pieces of information along with the data payload, ensuring the receiving system can recognize, authenticate, or process your request correctly.

Target Attendees: (for Attendee Webhooks only)

Apply filters to limit the webhook to specific attendees, like a particular ticket type, attendee type, language preference, etc.

Example:
Event Type: Attendee
Action: Create
Target: Sponsor ticket type
The webhook will notify you only when an attendee registers using the Sponsor ticket.