[Workflow] API - Custom Webhook
complete
Log In
Core Platform
Custom Webhook - LC Premium Actions
B
Bryan Stafford
Core Platform there is a major bug with this -
In a recent update you guys hard coded the content-type header and implemented a variable body entry system to account for json input vs x-www-form-urlencoded WHICH IS GREAT. However, only sending test requests (when attempting to save the response) actually sends form encoded data. When a workflow actually runs, it sends the form data as plain JSON.
It basically renders the x-www-form-urlencoded option unusable. See here for a demonstration:
https://www.loom.com/share/5220c23b45f24177979e1106ee871d95?sid=b57662ec-ed83-4e30-9bcc-4199befbb6db
Attached photos of the sample responses as well. Is this something that can be fixed with some haste? We are in the middle of a deployment and either have to build this fully inside the workflow builder or send the transactions out to Zapier and it would be a shame to have to double back after its fixed given it is released now and should work.
J
Jason Chagnon
Bryan Stafford did you ever get an answer to this? We have exact problem. Thanks for your post.
J
Joseph Castillo
This is great, but it still has a missing feature to send the body as application/x-www-form.urlencoded right now it allows only JSON and some API'S requiere application/x-www-form.urlencoded.
Daniel MacDonald
Encountering some issues with this functionality.
- Cannot override content-type header, always defaults to text/html
- "Send Test Request" requires re-selecting a contact. Every. Single. Time.
- Cannot save step / workflow without a successful test.
When you have to create workarounds to deal with (1), (2) becomes extra annoying. (3) is important due to general lack of auto-save and tendency to randomly lose work in the workflows editor.
This adds up to a lot of aggravation getting HL working with external systems!
Core Platform
complete
Core Platform
Custom Webhook - LC Premium Actions
Core Platform
in progress
Core Platform
Merged in a post:
Send Webhooks Without Standard Data
J
Jacob Radcliffe
We want an option to not send the webhook with standard data and to send the data without the default key "customData". Currently, the POST wraps the key/values in a key called "customData". If that is flipped off and it sends it bare, then we can send data payloads in whatever format we want including internal actions in HighLevel.
Core Platform
planned
S
Scott Heliker
I always thought the ability to sent request straight from a workflow with your own headers, json body, and query parametes would be cool. Then being able to use the return from that in the next step like you can with Twilio Studio.
C
Chris Stone
All I know is that this dude knows what he's talking about! To sum it up, this would help all Agency owners do a lot of automation without the need for 3rd party integration tools (like Zapier) since we would be leveraging the native actions the platform already can do (but currently has limitations).
Load More
→