1. Home
  2. AccessAlly
  3. CRM Automations
  4. [Guide] Webhook / HTTP post Commands & When To Use Them

[Guide] Webhook / HTTP post Commands & When To Use Them

When setting up automations inside your CRM, it’s important to understand the various HTTP post/webhook commands and how to use them.

Each time you add an HTTP post/webhook command in an automation, it syncs the CRM information with AccessAlly in some manner.

Take time to become familiar with each type of HTTP post/webhook command and their various use cases. Each tutorial will tell you which type of HTTP post/webook you should use. Using the wrong command will result in a membership site error.

 
HTTP Post / Webook commands are necessary for your automations, but many have ADVANCED USE functionality. Please read your automation tutorials carefully to understand which one should be used.
 

INFUSIONSOFT/KEAP - PLEASE READ

When adding an HTTP post to your automation, the Contact ID is already included in the Infusionsoft settings.

All you need to do is copy/paste your Webhook URL as outlined in this article.

ONTRAPORT - PLEASE READ

When adding a webhook to your Ontraport automations, you will have to add a unique post data for the webhook to work.

The post data is [Contact ID]

Please note: there must NOT be a new line at the end, or it won’t work.

CONVERTKIT - PLEASE READ

Because of limitations in the ConvertKit system, it is currently not possible to create a webhook directly. Please see this article for in-depth instructions: How to Create ConvertKit Webhooks.

 

Types of HTTP Post / Webhook Commands:

The base URL of your HTTP post/webhook can be found in AccessAlly > General Settings > Initial Setup

The bracketed [operation] portion of the URL is replaced by any ONE of the following commands:

aal_genpass This command generates a unique password for a user. Typically used in sign up/purchase automations.
aal_updateuser This command syncs permission tags for a user. Typically used only when updating permission tags for a SINGLE user.
aal_batchsync This command also syncs permission tags for a user. However, it is typically used when updating permission tags for MULTIPLE users.
aal_fieldop This command is typically used in a CRM automation for one of AccessAlly’s Custom Operations

If you are using the AccessAlly order forms, you will also be able to use the following:

aal_​revokesubscription This will revoke (immediately stop) an existing subscription.
aal_​cancelsubscription This will cancel an existing subscription, which means that the user’s card will not be charged for future payments.
aal_chargesubscription This will charge any outstanding balance for an existing subscription.
aal_createcoupon This will create an one-use coupon for a promotion.

Batch Sync Users (Advanced functionality)

The aal_batchsync operation is designed for a “timed” program release. A “timed” program release is configured when a group of clients receive new permission tag(s) at the same time.

How To Use It (example)

For example: a new module with permission tag “Module_3_Has_Access” is going to be released for 500 clients next Monday at 8AM EST.
At this time, the tag “Module_3_Has_Access” will be added for all 500 clients inside your CRM. The CRM automation will then notify AccessAlly that all 500 clients must have updated permission/access inside the membership site.
The volume of this HTTP request can cause a strain on the server resource. This may cause some of the requests to be bounced and not be completed, depending on the server’s capacity and security setting.

The “aal_batchsync” HTTP operation works around the issue by introducing a short delay (5 minutes) between AccessAlly receiving the update request and when it actually performs the synchronization, so the heavy duty operation is performed after the HTTP Post / Ping URL requests.’ section_head_2=’How to Use It’ section_content_2=’

“aal_batchsync” is configured very similarly to “aal_updateuser” in a Campaign (Infusionsoft) / Sequence (Ontraport) / Automation (Active Campaign).

After the permission tag(s) have been added, we can add a HTTP Post (Infusionsoft) / Ping URL (Ontraport) / Webhook (Active Campaign).

Because there is a delay between when AccessAlly receives the request and when the synchronization is performed, please allow a 30-60 minute delay (depending on how many users you have in the system) before sending the welcome email to the clients

Example Setup - Infusionsoft

To release the module at a specific time, the campaign needs to have 2 sequences: one to add the permission tag, and optionally another one to send the welcome or release email.

batchsync-ifs-campaign

In the release sequence, we will add the permission tag and send the “all_batchsync” HTTP Post.

batchsync-ifs-release-sequence

For the HTTP Post, the Post URL is (you can get the URL from AccessAlly -> General Settings -> Initial Setup -> System Integration)

http://site.url/?aal_batchsync=[handshake]

batchsync-ifs-http-post

Optionally, you can send a welcome or release email after waiting 30-60 minutes.

batchsync-ifs-email-sequence

Example Setup - Ontraport

To release the module at a specific time, the sequence needs to have 3 tasks: one to add the permission tag, one to notify AccessAlly, and optionally, one to send the welcome or release email after waiting 30-60 minutes.

batchsync-otp-sequence

For the Ping URL rule, the Post URL is (you can get the URL from AccessAlly -> General Settings -> Initial Setup -> System Integration)

http://site.url/?aal_batchsync=[handshake]

batchsync-otp-ping-url

Example Setup - ActiveCampaign

To release the module at a specific time, the sequence needs to have 3 actions: one to add the permission tag, one to notify AccessAlly, and optionally, one to send the welcome or release email after waiting 30-60 minutes.

batchsync-ac-sequence

For the Ping URL rule, the Post URL is (you can get the URL from AccessAlly -> General Settings -> Initial Setup -> System Integration)

http://site.url/?aal_batchsync=[handshake]

batchsync-ac-webhook

Troubleshooting a Slow Batch Sync

If you’re running a batch sync through your CRM, but it’s taking longer than 30-60 minutes to process all of the update requests through AccessAlly, it might be a setting on the web hosting server that needs to be updated.

Please contact your web hosting provider for your AccessAlly site, and ask to switch to a “system task based cron” so that the batch sync process runs quickly and efficiently on the server.

For example, the WP Engine Alternate Cron is a true cron that runs every minute on the minute, checking for and activating scheduled events. This is not enabled on your server by default, so you will have to request to have it enabled via Support.

Updated on April 26, 2019

Was this article helpful?

Related Articles

NO QUESTION GOES UNANSWERED

If you have any questions, we're just an email away at your@accessally.com.

We take your success seriously, and you'll always get a speedy reply from a real person during business hours.

AccessAlly is the #1 WordPress Course and Membership Solution for Industry Leaders

WATCH THE DEMO

You'll get follow-up emails about AccessAlly and new features. Opt out anytime. Full privacy policy here.