Outbound Webhook

How do we send out a Webhook at the time of registration, and how about audience qualification? Setting it up is easy...

AEvent avatar
Written by AEvent
Updated over a week ago

Pairing AEvent with an Outbound-WebHook can get you the data you want, where you want, when you want, and gives you total control over HOW that happens.

You can set up Outbound WebHooks to trigger both On-Registration and a timeline action (say all Cart-Abandoners).

It's easy to set these up, and every piece of data you could want is formatted and sent in the outbound webhook call.

Timeline Actions:

Adding a new Webhook as an AEvent Integration

In order to set up a WebHook, you need to add it as an Integration. To do that, first navigate to Integrations within AEvent, click Add Integration, and then select WebHook.

Then, name your integration as you see fit and click 'Add.' (With Webhooks, we would recommend an easy identifier, as you may end up adding several Webhook integrations).

Now define the URL Endpoint of your Webhook, as well as Type, Structure, and Encryption.

(In general, POST, JSON, and Encryption OFF work best)

Once your new WebHook integration has been successfully added, you will be see it's Connected state, and you are able to click on 'Test'.

A successful connection will yield a positive test result AND will send a payload test packet to that endpoint. Congratulations, your Webhook is now connected to AEvent and can be set up within a timeline!

Configuring your Webhook Integration within a Timeline

In order to utilize your Webhook within AEvent, you need to activate it within the timeline you are working with. To do this, open the timeline you are working on.

Then, select Integrations, set your Webhook as Active, and click on the cogwheel.

If you do not (by default), this will send an outbound webhook with each new registration. If you want to use this within the timeline as Audience qualification, you need to disable this from occurring on-registration.

And that's it. If set as active, all new registrations to this timeline will make an outbound call to this Webhook Integration.

Creating a Timeline Action to Send a Webhook Action.

Within our timeline builder, you can set a WebHook action to occur at any point before, during, or after your event.

Our best practice recommendation would be to utilize WebHook timeline actions for precise audience targeting after your event.
It could be something as simple as an outbound WebHook for all attendees or non-attendees of the event. But you could go several layers deeper utilizing our Audience Segmentation options. In this tutorial, we will build out a timeline action that targets Cart Abandoners.

Per the example above, at 8 AM the day after the Event a outbound WebHook action would trigger for anyone that was a Cart Abandoner from our event.

In this instance, I have elected to send the information Per Registrant. By selecting this, the system will send an individual WebHook call per registrant. If I hadn't selected this, the information would have been sent as a single payload packet. (Generally, you want to check this unless you're a super-whiz)

After clicking Create, this action is now visible on the timeline.

How to remove your WebHook from AEvent

If you want to remove your Slybroadcast integration from AEvent, you need to navigate to Integrations, locate your Slybroadcast integration, and click on the trashcan icon.

You will then be prompted to confirm the deletion.

(NOTE: Removing this integration will immediately affect its use with any timelines that it is active in.)

If you are experiencing issues with this integration but do not desire to REMOVE it, we recommend reconnecting it instead. This will allow it's configuration to

continue as set within your timelines.

Once you confirm removal, the integration within AEvent no longer exists.

Layout of our Webhook payload (Per Registrant, customfields on the end)

"subscriber": {
"uuid": "registrant uid",
"firstname": "First Name",
"lastname": "Last Name",
"email": "Email",
"phone": "Phone Number",
"ipaddress": "IP Address",
"registrationdatetime": "Registration Date Time",
"joinurl": "https://joinevent.link/tenantid/registrantuid",
"customGroups": "Attendee, GroupName",
"timezone": "Timezone",
"country": "Country"
"webinar": {
"webinarID": "Gotowebinar True Webinar ID",
"timeZone": "America/Denver",
"timeStamp": "Webinar Start time",
"dayofweek": "Day of the week",
"dayofmonth": "Day and Month",
"day": "Day",
"month": "Month",
"year": "Year",
"esttime": "Time in Eastern Timezone",
"pasttime": "Time in PST Timezone"
"replay": {
"webinarID": "Gotowebinar True Webinar ID",
"timeZone": "America/Denver",
"timeStamp": "Webinar Start time",
"dayofweek": "Day of the week",
"dayofmonth": "Day and Month",
"day": "Day",
"month": "Month",
"year": "Year",
"esttime": "Time in Eastern Timezone",
"pasttime": "Time in PST Timezone",
"replayURL": "Replay URL"
"customfields": {}
Did this answer your question?