The Webhook trigger in HighLevel workflows is a very useful tool to enable us to connect third party tools into HighLevel. So effectively push contact and other information into HighLevel.
The one slight niggle is that in order to SAVE the webhook trigger you must first TRIGGER the webhook.
Now sometimes this is not a problem – just go to the third party tool and trigger the web hook as a test.
Other times it is a problem. Say for example you are getting leads form a third party. You send them the webhook URL to add to their system and then it takes them say hours or days to incorporate it into their system before even thinking about testing the webhook. So this effectively means you cannot close you browser or PC for fear that you lose the unsaved webhook. Because if you do, you cannot get that unique webhook URL back. It is gone and you have to start the entire process again – which is a huge pain in the butt.
The solution.
Trigger the webhook with some very basic data that will at least enable you to save the webhook URL and keep the URL safe. It will mean coming back to it at some point i.e. the first time the webhook fires for real, with real data. But at least it enables us to save the precious webhook URL and enable us the complete the rest of the workflow BEFORE the webhook goes live.
How to do this.
This is very straight forward. Take the webhook URL and add something like this to the end :
?first_name=testfirstname&last_name=testlastname&email=test@test.com
Then paste this into a browser window and press return.
You will see a success message to indicate that you have triggered the webhook.
Go to your webhook trigger in the HighLevel workflow.
You will see a box for MAPPING REFERENCE – Fetch sample requests. Click on this and you will see an option for Select Reference Payload.
From here you should now see an entry for your test submission. You can now use this test submission to complete the Webhook trigger set up, and set it up to create a contact by using the dunny data that the test submission pushed into HighLevel.
Now you can SAVE the workflow.
Then later on, the first time the webhook fires for real then you can come back in here, go to MAPPING REFERENCE – Fetch sample requests and pull in the first real data submission. And from this you can then tweak your workflow to first set up a contact record and later on use the additional data contained in the webhook to update the contact and do all sorts of automation based on the data contained within the webhook.
Julian
