Tutorial: Zapier Webhook → Zoom

Create a new Zap

Add the 'Webhooks' trigger

Add the initial trigger for your zap and search for the “Webhooks by Zapier” action.

The Webhooks by Zapier action requires a Premium Zapier account.

Configure the Webhook

Click on the action to open the webhook settings.

1. Under the “App & Event” tab, keep the Event as Catch Hook. Click Continue.
2. Under the “Trigger” tab, keep the settings. Click Continue.
3. Under the “Test” tab, find your webhook URL and copy it.

Zapier is now listening for applications sending data to this URL. We’ll leave the Zap here for the moment and come back to it in a later step.

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. Copy the ID without the spaces.

Register the Zoom ID with your Tightknit Event Webhook

We need to include the Zoom ID in the data sent to the Zap so that Zapier 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

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. Register for your own Tightknit event in Slack. 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 Zap

Jump back to the Zap editor from earlier. Under the “Test” tab, click the Find new records button. You should see at least one record of your registration test run in the previous step. Select the record and click Continue with selected record.This sample data will give us useful visual aids in Zapier 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 Action to Zap

In the Zap editor, click the + to add a new action. Search for the “Zoom” action.

Configure Zoom Action

Click on the Zoom action to open the settings. We will instruct Zoom on how to register a new user based on the incoming data Tightknit sends to Zapier.

1. Under the “App & Event” tab, select Create Webinar Registrant or Create Meeting Registrant, depending on your Zoom event type. Click Continue.
2. Under the “Account” tab, login to to your Zoom account. Click Continue.
3. Under the “Action” tab, configure the following fields:

• Upcoming Webinar - 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 tab, search for “Custom Metadata”, and select the “Custom Metadata” option associated with the webhook trigger.
• Email - select the “User Email” field from the webhook trigger.
• First Name - select the “User First Name” field from the webhook trigger.

You’re free to fill in any additional fields as you like. 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.

Do NOT hardcode the Zoom action input values. It’s an easy mistake to set the Upcoming Webinar to a specific Zoom meeting in the dropdown list. 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.

Test Zoom Action

Publish and Enable the Zap

Click the Publish button in the top toolbar to save your changes.Next, click the On/Off toggle in the top-left of the toolbar to enable your Zap. It should show a green On.Your Zap is now live and ready to forward your Tightknit event registrations to Zoom! 🎉

BONUS: Add Branching Logic for Register vs. Unregister

Right now, our zap assumes 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 zap 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.Add a zap action in between the Webhook and the Zoom actions. Select the Paths by Zapier action, and configure each branch as follows:

• Name the left-side branch “Registered”. Choose a custom rule that will continue if Status exactly matches “registered”.
• Name the right-side branch “Unregistered”. Choose a custom rule that will continue if Status exactly matches “unregistered”.

Zapier Limitation
Zaps that contain the Paths action cannot be copied or converted into a template.

Move the Zoom action under the left-side branch. When you’re finished, your zap should look something like this:You must add some action under the right-hand side too before you can publish the Zap. If you’d rather just completely ignore unregister events, you can use the Filter Zapier action instead of Paths, and only continue if Status exactly matches “registered”.

Don’t forget to republish the Zap!