Ive been using webhook to receive information from a company, so im notified whenever a check is created. And I had a challenge getting it to work and after getting it to kinda work, Ive come to thee following conclusions with the webhook node in the hosted cloud n8n:
The webhook url is not changeable by us, yet it does seem to change, in a buggy way, at one point my production url had the test url and a weird hybrid version, and I could not alter it or change it so I had to delete the node and start over. I would say that is a bug, and the reason my testing was failing. Its coded poorly or something. Has anyone else noticed this. Is there a place to post bugs like this? im not seeing any in this community , so far. I am new. I feel the nodes save automatically on their own and load thee parameters on open and that process is buggy and omits and changes the parameters, in the webhook node specifically, as im seeing the parameters change when opened sometimes.
I also notice another buggy behavior, is that you can add actions to it and i would add a response code and set it to 200, and it would show and when I closed it and save and go back later this action was GONE. and I had to re-add it over and over. as you can imagine this made testing once again a challenge cause things were failing because parameters would UNSET themselves.
Your post is a little confusing. Where is the webhook node in the workflow you included?
It could be that the latest versions of the editor have introduced some bugs, but when I have observed what you are describing, I often find that I had another browser window or tab open in the same workflow, and I was overwriting my own changes (not saying that’s it… just something to double check).
Re: #2, That does seem like a bug if you add the Response Code option and leave it set to the default value (200). If you set it to anything else, it doesn’t vanish. That’s sorta annoying, but then, there’s really no point to adding that option and leaving it as the default value anyway, so I bet it doesn’t come up much. If you wanted to report it, you could open an issue on the github project.
are you saying that it defaults to a response code of 200 and it doesn’t need to be set? Hmmmm, if that is the case then maybe thats why it disappears. But still if we set something, it should remain set, regardless. I set it because the sender of the webhook would return an error if they didnt see a 200 response indicating success. So it didnt really return 200 unless I set it as a specific action.
Typically, an http service will return 200 by default on a successful call. See: The http RFC Docs. You are right though, if you add an option on a node, whether or not you set it to a non-default value, you shouldn’t have to add it again. There is probably just logic missing that distinguishes between “option added” and “option value is/isn’t default.”
im receiving follow up emails asking me to select an answer and or reply back letting you all know . That is odd, as it does not seem to fit me with this issue.
My issue wasnt resolved, and seems like a bug in the software. So not sure what to do. Im too busy to also report a bug, and even if I did, reporting a bug doesn’t seem to be a choice I was given. Just choose an answer or give more info. Odd indeed.
