Skip to main content
How to use Webhooks

Utilizing webhooks to transmit revnt data to other tools and platforms, especially through Zapier.

Written by Chris Deardorff
Updated over a week ago

Webhooks are a powerful and flexible way to connect the revnt platform to nearly any other application you utilize within your organization. Either directly, or through Zapier, webhooks can send data to your other applications anytime an event or user action occurs within the revnt platform.

Utilizing webhooks does not require you to be a programmer or to write any code, however it will be helpful if you have a basic understanding of APIs and/or how data can be sent between multiple applications as JSON. If you’re unfamiliar with those concepts, or just want a refresher, I recommend you start by reading this helpful guide by Zapier before moving forward.

Getting Started

For the purposes of this guide, we’ll utilize Zapier to create our webhook, but the same flow will work for any API or other connection that supports receiving JSON data via a POST request.

Create the Endpoint

Note: If you don’t have a Zapier account, you can sign up for a free account to understand how the process works and determine if it is something you want to utilize. However, if you wish to use our webhooks, you will need to have subscribed to at least their Starter Plan.

From the Zapier dashboard, click the Create Zap button on the top left of the dashboard:

Once here, go ahead and select Webhook, then choose “Catch Hook” for the trigger event, and finally “Continue” to get your custom webhook URL.

Once you hit continue, go ahead and copy the URL, then return to the revnt platform:

Setting up the Webhook

Back in the revnt platform, go to your organization’s dashboard by clicking “Manage Your Organization” in your user menu. Once there, click the gear icon on the top right to manage your organization’s settings:

Then click add webhook and paste the URL you copied above into the URL field:

By default, your webhook will be subscribed to all available events, but you can optionally deselect certain events to avoid hitting your endpoint quite as often or having to filter out unneeded data later. Click here or scroll all the way down to see the “Webhook Event Types” table for information on each event type and the data it includes.

For our purposes, make sure at least ‘Event Registration’ is still selected, as that’s what we’ll use to finish setting up our webhook.

Triggering Your Webhook

Before going forward, switch back to Zapier and ensure that it’s ready to receive your event. The view should look like the screenshot below, if not make sure to click Continue at the bottom of the previous view where we copied the URL:

Back in the revnt platform, click "Test Webhook" underneath the event selection field. This will automatically send example data to the URL you specified for each event that you’ve selected.

Once the data has been sent, go ahead and head back to Zapier and click “Test Trigger”, where you should see a captured request that looks similar to this:

To view the test data for each type of event sent by the revnt platform, select each request from the dropdown.

You should be able to see all the data that was sent as part of the webhook, including the event that you registered for, the email address you used, along with your participant profile and any registration responses as well!

For the purpose of this guide, make sure you have selected the request labeled hook_type: event.registration at the top of the example data. In the above GIF, it's Request B, but it may be a different letter in your instance.

If the data transmitted successfully, go back to revnt and click Save.

Note: Currently, webhooks apply to all events under your organization. The ability to use webhooks on a per-event basis is on our roadmap.

Utilizing Your Webhook

Ok, we’re in the final stretch now, almost done! Now that we’ve told Zapier what kind of data we’ll be sending, all we have to do is tell it what to do with that data.

Click Continue again, and now we can select where we want to send this data. For our example, we’ll just write it into a Google Spreadsheet, but you can send it to any app that Zapier supports with just a few clicks!

Click "Google Sheets" and select “Create Spreadsheet Row” as the action. You may need to sign in to Google if you haven’t connected Zapier to Google Docs already to allow Zapier to make changes in your spreadsheet.

From here, you can select any spreadsheet already in your Google Drive (unfortunately you do need to create one manually, Zapier won’t auto-create one for you in this flow), and then you can select how to input the data. I’ve created an example spreadsheet with four columns (Zapier will automatically detect column headers and bring them in).

If you like, click here to view my spreadsheet and copy it to your drive: Example Zapier Sheet.

For each column, specify the value that you want to fill in by searching in each text field.

Now simply hit Continue, followed by Test and Continue to run the action based on your original test data, then go to your Google Sheet to confirm it worked:


Congrats! You have now successfully connected event registrations within revnt to your Google Sheet! Using the same flow, you can easily connect them to your CRM, newsletter mailing list, or almost anything else!

Webhook Event Types

Event Registration

This event will trigger every time someone signs up for your event. You’ll receive information about the event itself, the attendee’s basic profile, as well as their responses to any registration questions you attach to your event.

Event Viewership

This event triggers anytime the overall analytics for your event update (or for an individual session), based on live and on-demand viewing of your session(s). These analytics are calculated once per day for as long as your event is hosted on the revnt platform.

User Viewership

This event will trigger with the individual viewership statistics for each individual attendee, both when they first watch your session(s) and when they return to review any part of it later.

Did this answer your question?