Hey happy Thursday everybody Sean coming At you from high level I know how can we Continue to pound out all these amazing Releases I don't know it's just that That team is so fantastic so check this Out today we've got another Um enhancement on the inbound web hook Trigger so what the heck is that so First let's just jump in over the Screenshot so in the workflows there is An inbound web hook an inbound web Hook Is literally basically we're giving you A URL and we're saying listen you can Send data into high level from anywhere You darn well please and do stuff with It in a workflow in real time that's What an inbound web Hook is but today we Are going to enhance that quite a bit as You can see so a couple of things new Methods allowed you can do uh and this Is this is a little techie so don't Don't if you like feel like I don't know What that is don't don't uh you know Don't worry um it's all good but for Those of you do it's uh you can do a get Method you can do a put method you can Do a head you could do it options Um and then spaces and custom values now Work across the workflow app query Parameters and headers are accessible Inside the workflow so if you pass query Members in like on a get request or There's header parameters that are Coming in you can also do that and
There's UI enhancements okay so how does It work for all custom variables but Mainly in bad web Puck ones you can use The spaces to reference them so for Example Inboundwebhookrequest.shopify space Product space purchase will Now function Perfectly whereas before it would not Um we will edit that in the back end to Match key dot key with space the Handlebars will accept it no changes Required in the setup uh and the spaces Are uh that that is in setups where Space is already there you don't have to Do anything basically it will now just Work besides posting by what I'm posting I'll do get and put methods they'll Function exactly the same and store the Data in the uh in the same way they'll Appear together with the post request When mapping the reference head and Options methods will simply return 200 Success responses so that way third Parties like Thrive card for example and Others can hit us and confirm the Endpoint exists and is valid so Um real quick there um for those who Wonder what that is basically when You're setting this up let's say there's System there's a system out in the world That's going to like sort of shoot over To us but some of those systems will Honest often do it's like send a little Ping essentially to see like is that URL
Like legit and real and works and They'll send it via head quote unquote Or options request type and we're just Going to say 200 which means like A-Okay So that way they recognize that the web Hook is valid so that's awesome job now Headers will be saved inside the request Payload so headers um gosh sort of super Taggy here but just basically in Addition to the request itself you can Set up sort of these additional things That come in and they're called headers And now they're also actually available In the workflow which is Awesome by the Way query parameters sent me a URL will Also be saved inside the request payload Um and it's generally well and actually Ironically enough I mean I would say Well generally that's only for a get Request and this and that um but you Know you can you can still do it with Other request types as well so it's Awesome to team rock that out Um and uh why is this important all Third party apps that have about Web Book integration should now fully Function with us in order to the only Case where it won't is when there's a Lack of phone or email reference to a Contact although we are working to fix That Um so AKA right now today every workflow Is really contact based right so you Really really focused in around a
Contact of some kinds or like literally Creating the contact essentially or or We have a contact in each case but what Is really important here is if you have A contact that you're trying to Reference versus create a new one you Can see you simply can add like email Equals integration at contact.com to the End of the workflow URL and use that as The main contact for the iterations this Is kind of like a workaround for the Moment if you aren't referencing a Contact directly in the inbound web hook So anyways uh let's look at a couple Screenshots and then close her out so Here is the workflow trigger you can see When you choose it you'll get a URL Where you can see you can post and get And put and then when you're ready uh When you've done that you can hit fetch Sample requests and then once that comes Back we'll gather those requests show it To you and then you can actually use That to actually map in all the data Subsequently in the workflow steps again This is sort of like an advanced thing So like for any of you who are wondering When would I ever use this if you're Wondering that you probably won't right But if you're really um trying to Interconnect external systems to high Level this is an amazing way to do it so Anyways awesome awesome job by the Workflow team as you can see right here
There are help articles so for example You can search how to use the in battle Web hook workflow premium Trigger or I Would just search inbound web hook and I Bet you money it'll come up um or you Can also do uh well actually I think That's the same thing yep yeah so that That is the help article for that so on That note um I think I've got one other Video to go otherwise I hope all of you Are having amazing Thursday and we'll Talk soon bye
