All Collections
Connecting iQualify to other systems
Event Hub
How to configure webhooks in the Event Hub
How to configure webhooks in the Event Hub

Account owners can configure webhook endpoints to automate processes or generate reports outside iQualify

Caitlin Foran avatar
Written by Caitlin Foran
Updated over a week ago

As an account owner, you can set default webhook endpoints to collect events, event data or configure individual events to individual webhooks. 

Any events that have not been individually set and are turned on will send their data payload to the default endpoint.

To begin setting your webhook endpoints first navigate to the Event Hub which can be found here:
iQualify Settings > Integrations > Event Hub

If you are uncertain where to find this area then please read this article on iQualify settings.

Ensure that the Event Hub is turned on. This will enable the other settings.

Setting a default webhook endpoint

Simply input your webhook endpoint into the Endpoint field under Default settings and select enable.

You can also add custom header data that will be sent with the event by clicking Add Header.

All events that are turned on and do not have an individually set endpoint will send their payload to this webhook.

Setting a webhook endpoint for an individual event

To set individual event webhooks, first select the category of the event that you want to configure using the drop down menu.

This will show all available events in this category. In this example Content has been selected.

Events that are enabled will display a green tick in the corresponding event icon. If that event has been turned off then the icon will display a cross.

Select the event that you want to configure. In this example we will select Submitted a practice quiz.

First ensure that the event is enabled then input your individual webhook endpoints into the Endpoint fields.

You can also add custom header data that will be sent with the event by clicking Add Header.

Anonymising event data 

You can also remove data that identifies the users that actioned the event from the payload.

For example you may want to generate statistics about how many times a quiz has been accessed but you are not interested in the identity of those individuals that have accessed it.

To capture the event but anonymise the data, turn Anonymous on for the individual event.

Did this answer your question?