Inbound Webhook Response (Respond to an *inbound* webhook trigger)
D
Donald Moore
Now that we can save the response from an outbound webhook inside of a workflow, if we could now get a response from an Inbound Webhook Trigger, we could eliminate the need to match custom values and custom fields to their respective hashed IDs in the system.
This way, you could basically use HighLevel like a stateful "headless" CRM without the pain of having to create tables of Custom Values and retrieve the hash each time you create a Custom Value or a Custom Field.
Log In
E
Ed Preble
Often third parties who are sending data to my webhooks are looking for a response and I'm unable to provide them one unless I use Make which in turn causes me to use them for other stuff that should be done in GHL. I'd rather stay on one platform.
D
Donald Moore
For example, in Make you can respond to an inbound webhook after processing some data. Since we can now store webhook responses in Workflows (https://www.loom.com/share/263fe3fbc175464aab9b9d8a5fc84659?sid=20f4a154-53fc-4594-8ffb-c7444674595c), this would basically make HighLevel a headless CRM.