When BatchSync Webhooks Are Required In Your Automations
If you are running multiple users through an online course simultaneously, we recommend that you use the batchsync webhook, to prevent the integration from timing out or becoming overloaded with multiple individual requests.
Tutorial: How to Create A BatchSync Webhook For ConvertKit
This tutorial walks you through each step of the process to create your own tag-initiated batchsync webhook for ConvertKit.
Step 1: Create A New Tag
Inside ConvertKit, create a new tag that will be used to trigger the batch sync webhook. (Example tag name: accessally_batch_sync)
Step 2: Enter ConvertKit API in Webhook Creator
Step 3: Select Your New Tag
Once your API information is saved, new settings will be revealed. In the “Select the trigger tag” area, you can select the tag you created in Step 1 of this tutorial.
Step 4: Enter the batchsync webhook URL
If you are not sure what your webhook URL is yet, follow these instructions.
Then, chance the aal_genpass portion of the URL to aal_batchsync.
Step 5: Create Webhook
Click on the yellow Create Webhook button.
Adding the Webhook To Your ConvertKit Automations
Step 6: Add “Batchsync” tag to CRM Automation
When building your ConvertKit automation, you can now use the accessally_batch_sync tag instead of the generate user tag that you configured in AccessAlly’s General Settings area.
Step 7: Add Delay
After you add the accessally_batch_sync tag to your ConvertKit automation, make sure to follow it immediately with a delay, so that the function can be run properly.
Step 8: Remove BatchSync tag
Finally, remove the accessally_batch_sync tag in your automation so that it can be run again whenever needed.