1
Create a new Scenario
To get started, open the scenario editor in Make and create a new scenario (instructions).
2
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.3
Copy the Webhook URL
Locate the URL for your webhook and copy it. You can also click the 
Copy address to clipboard
button.
4
Register the Webhook URL with Tightknit
In the Tighktnit webhooks admin portal, create a new endpoint using the webhook URL from the previous step.
5
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. Copy the ID without the spaces.

6
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 
Under the Registration Settings section, configure the following:
Events
button in the app home or by typing the \events
command. Click the •••
menu next to your event and select Edit
.
- Check the checkbox to Enable Webhooks.
- Paste the Zoom meeting ID into the Webhook Custom Metadata field
7
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 

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 
Run once
button.

•••
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.
8
Verify Data Received by Make
In the scenario editor, you should see that the scenario run was completed. Click the 
This sample data will give us useful visual aids in Make when selecting fields from the webhook data.
1
bubble above the webhook module. This will show you the data that the webhook received from Tightknit.
The shape of Tightknit’s webhook data may change. Please check the API
docs for the latest.
9
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.
10
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.
11
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! 🎉

12
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 
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
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
status
is equal to “registered”. - Name the second branch “Unregistered”. Create a condition that will continue if
status
is equal to “unregistered”.

status
is equal to “registered”.Don’t forget to save the scenario!