Triggering direct mail from your HighLevel CRM is made to be simple when set up through the Postalytics/HighLevel Integration option. Once your Triggered Drip Campaign is set up, Postalytics will be “listening” and ready to receive your data for print, mail and tracking. 


Follow the steps below to get started. 


Within your Postalytics account, navigate to the Connect page, found in the drop down menu under your user name.


Next, click on "API Key" on the left hand side. This page contains the private key for your account for all webhooks to your account: it's the key that tells us you are you. Notate down, or copy the "Authorization Header", as this will be required for use later within your HighLevel workflow webhook. 


Now, head to the marketplace by clicking on “Connect App Marketplace'' in the upper righthand corner, then select “details” under the HighLevel icon. You’ll be taken to the following page:



Click "Add Integration", which will bring up a wizard to walk you through the steps needed to create the integration. The wizard allows you to create a custom name for the connection, as well as listens in for a test to make sure the correct mapping comes through. Leave this window open for now.  



Next, open another tab and navigate to your HighLevel account, then head to Automations > Workflows to create a new workflow.


For the workflow to set up the connection, use the trigger "Contact Changed". This will start the workflow upon any contact within the system changing its details. 


Next, add an action, and search for the action "Webhook". A webhook here will be used to send data to Postalytics from your various triggers for Triggered Drip Campaigns.


In the webhook, you’ll set up the following details:

  1. Set the method to POST. 

  2. The URL will come from the wizard window left open in Postalytics. 

Under "Send a test Webhook from HighLevel", there is a test URL available to copy, this is the listening point we will be sending the initial set up to. Copy this URL and paste it into the URL field of the wehbook action within your HighLevel workflow.


In the fields under "Custom Data", add the following information to pull from your account. Fields notated with an Asterisk (*) are required.

  • First Name* 

  • Last Name*

  • Address*

  • Address2

  • City*

  • State

  • Zip

  • Contact Id

  • Website


Under "Headers", add two sections. 

The first is "Authorization", and the data field is the "Authorization Header" that you notated or copied from the Postalytics “API Key” page. 

The second is "Content-type" and the data field is "application/json"


Your webhook should resemble the following:



Save your webhook. 


Now it is time to test to make sure the workflow is active. 

In the upper left-hand corner of the window, click the "Test Workflow" button, and select an account to test with. 


Return to the open wizard window in Postalytics. You should now have the ability to map the fields coming in from HighLevel to the proper fields used by Postalytics. 


For each field, scroll through and match them together.  



Click complete once they are mapped properly. Your HighLevel integration is now ready to use!


To use HighLevel for a specific campaign, you’ll need to create a new Triggered Drip Campaign, selecting HighLevel as source of data, then completing all of the remaining steps to set up the campaign.


Once your Triggered Drip Campaign is set up, some of the details from it will need to be added to the webhook workflow created within HighLevel. 


Open your campaign list, find the newly created campaign, click on the ellipsis next to it, and select "Settings". 


This will bring you to a page with the information about your current active Triggered Drip Campaign. 


 


Copy the "Webhook Url", and add that as the URL in our HighLevel workflow webhook instead. 

The original URL used in the set up step was a test URL for the initial connection only. 


Each campaign you create will require its own HighLevel workflow webhook pointing to the individual Triggered Drip Campaign's specific URL.  


Additionally, all workflows in HighLevel will need to be flipped from draft mode to publish.