Posts as x-www-form-urlencoded don't work about webhook HOT 7 CLOSED

Thanks for the write up! I'll take a look into this as soon as possible and will post you with an update and a solution... :-)

The thing with the form-encoded payload in webhook at the moment is that you can only get values of the passed variables, in your case being payload variable with the JSON payload. So basically you can pass that JSON string to your script and then parse it inside and extract the values you are interested in.

I will see what modifications can I incorporate into webhook to make it easier for this scenario...

from webhook.

I'm thinking about adding a property on the hook named json-parameters which would contain a list of parameters that the user expects to contain JSON strings. Upon receiving the request, webhook would then try to parse those values as JSON and the user could use them just like the parameters in JSON formatted payload. (parameter.key.anotherkey). Solving the issue you currently have... What do you think?

from webhook.

So as an example, I could define "json-parameters": [ "mypayload" ] in hooks.json, and webhook would decode the mypayload form variable as JSON. Then I would reference the JSON items like this:

{
  "match": {
    "type": "value",
    "parameters": {
      "source": "payload",
      "name": "mypayload.commits.0.branch"
    },
    "value": "needle"
  }
}

I like the idea.

However, json-parameters sounds a little ambiguous to me. It might confuse people into thinking it has something to do with the match.parameter triggers from the hook package. What about http-json-parameters? But either way, you make the call. It'll be great. 😄

from webhook.

Exactly that. Maybe parse-parameters-value-as-json? :-)

from webhook.

I'll get this done tonight.

from webhook.

Success!!

from webhook.

Awesome! :-)

from webhook.