Tutorial: Make Webhook → Zoom

Create a new Scenario

Add the Webhook trigger

Add the initial trigger module and search for “Webhooks”. Select “Custom webhook”.

Click the Create a webhook button. Give the webhook a name such as “Webhook for Tightknit Events” and click Save.

Copy the Webhook URL

Locate the URL for your webhook and copy it. You can also click the Copy address to clipboard button.

Register the Webhook URL with Tightknit

Get Zoom Meeting ID

Log in to the Zoom online portal and navigate to your Meetings/Webinars. To work with Zoom’s registration APIs, we simply need the ID of the meeting/webinar, which you can find in the details of the event.Important: Copy the Meeting ID as a continuous number without spaces. For example, if Zoom displays 883 3309 6147, you should copy it as 88333096147.

Register the Zoom ID with your Tightknit Event Webhook

We need to include the Zoom ID in the data sent to the Make scenario so that Make knows which specific Zoom event the user registered for.Open the Tightknit events list in Slack by clicking the Events button in the app home or by typing the \events command. Click the ••• menu next to your event and select Edit.

Under the Registration Settings section, configure the following:

1. Check the checkbox to Enable Webhooks.
2. Paste the Zoom meeting ID into the Webhook Custom Metadata field, without spaces.

Click Save.Tightknit is now configured to send registration data to your webhook endpoint, including the Zoom ID.

Test the Tightknit Webhook

It’s easier to work with sample data, so let’s do a test run. In the scenario editor, click the Run once button.

Make will be listening for incoming webhook data.Now, back in Slack, register for your own Tightknit event. You can do this by clicking the ••• menu next to your event and selecting the registration option.

The exact label of the registration option may differ depending on your community’s configuration.

Verify Data Received by Make

In the scenario editor, you should see that the scenario run was completed. Click the 1 bubble above the webhook module. This will show you the data that the webhook received from Tightknit.

This sample data will give us useful visual aids in Make when selecting fields from the webhook data.

The shape of Tightknit’s webhook data may change. Please check the API docs for the latest.

Add Zoom Module to Scenario

In the scenario editor, click the + action by hovering over the side of the webhook module. Search for “Zoom” and select the “Add a Meeting Registrant” or “Add a Webinar Registrant” action, depending on your event type.

Configure Zoom Module

Under Connection, log into your Zoom account to authenticate the Make connection.Configure the Zoom module as follows:

• User ID - Select your user id from the list
• Meeting/Webinar ID - this will be the ID of the Zoom meeting/webinar, which we’ve configured Tightknit to send in the Custom Metadata field of the webhook data. Select the custom_metadata option associated with the webhook trigger sample data.
• Email - select user: email.
• First Name - select user: first_name.

Do NOT hardcode the Zoom action input values. It’s an easy mistake to set the Meeting/Webinar ID to a specific Zoom id. If you accidentally do this, users that registers for any event in Slack will always be forwarded to that one particular Zoom meeting, even if they were trying to register for a different event.

Keep in mind Tightknit will also send along any custom profile fields configured for Slack profiles in the workspace (example). Consider adding some profile fields if they would serve as helpful user registration info.

Save and Enable

Click the 💾 save button and switch on the toggle to enable your scenario.

Your Make scenario is now live and ready to forward your Tightknit event registrations to Zoom! 🎉

BONUS: Add Branching Logic for Register vs. Unregister

Right now, our scenario assumes that every time data is sent to the webhook it means a new user has registered for an event. Technically this is not true! Tightknit sends other kind of data too, such as a user unregistering for an event.Let’s assume you want to take some sort of action, or simply ignore, an unregister event. We’ll need to add branching logic in the scenario in order to differentiate based on the incoming data. In this case, we’ll create a branch based on the status field of the Tightknit webhook data.Click on the wrench icon in between the Webhook and the Zoom actions. Select the Add a router option. In order to add a new branch to the flow, click the Router module itself. On each of the branches, click on the wrench icon and select Set up a filter.

• Name the first branch “Registered”. Create a condition that will continue if type is equal to “calendar_event.user_registered”.
• Name the second branch “Unregistered”. Create a condition that will continue if type is equal to “calendar_event.user_unregistered”.

When you’re finished, the scenario should look something like this:

If you’d rather just completely ignore unregister events, instead of using the Router you can simply add a filter on the path to the Zoom module with the condition the flow will continue if status is equal to “registered”.

Don’t forget to save the scenario!