Hi,
We noticed that our workflows designed to trigger webhooks in Make are failing. We use these webhooks daily, and no changes have been made to either the Noloco workflows/webhook or the corresponding Make Scenarios.
Below is the Noloco error we received from an on-demand workflow run:
Invalid webhook url
Your workflow webhook action has an invalid webhook url. Review your workflow configuration.
Same here. I looked at my workflow configuration and there was a field in the URL parameters that I needed to removed and then it worked. It was a field that never would have worked before (Project Name, which contains spaces) but somehow it was there. Might want to walk through any dynamic fields in your webhook URL to make sure nothing get loaded in there in error.
Cheers @jesse I checked one workflow and removed two variables that would contain text values and then ran a Test (within the workflow area) - that worked. However, when i try via the app (this workflow is triggered by a button), it failed again. Same error.
This was working two days ago… so, not sure what has changed. It’s not the only one that is now failing - I don’t really want to go through all our workflows testing variables.
@Noloco - has something changed in the last couple of days?
Hey @cizict we haven’t changed anything about how workflows trigger webhooks in the past few days.
If you reach out to our support team with the link to the workflow, and the timeline, we might be able to help you figure it out.
It does sound like something @jesse flagged though, with special characters in the webhook URL
Hi Darragh,
Thanks for the response. Yes, there are special character like spaces & hyphens coming in from some of the dynamic values like “Business Name” in the attached example, but these ran without an issue, using similar data, from about 2 days ago - see screenshot attached from Noloco & Make.
Maybe you were encoding the dynamic values in the URL previously?
@Cillian_CizICT I’ll check with the team to see if anything changed, but to my knowledge we didn’t change anything.
Could it be in how Make accepts the webhook?
It does look like a recent change we made could be the root cause of this, our team are working on a fix now.
One thing I’ll add, while that’s worked on, is that you shouldn’t need to add URL parameters if you’re trying to get values from the trigger record (as in your example @Cillian_CizICT ) as you can see from your screenshot, the full record is in the webhook payload.
So the quick fix would be to remove those parameters from the noloco config, and then rely on the webhook BODY rather than the parameters, in Make.com
We will update you if we confirm it’s an issue, and have a resolution.
Quick update - the team do think a recent change that improved security of Noloco, falsely flagged URLs with spaces in them as malicious and caused these to fail, this will be fixed today, hopefully within the next 2 hours.
Thanks for helping us figure this out @Cillian_CizICT and @jesse
Thanks for looking into that @darragh .
That workflow is related to the Projects table, but we need to send details from other tables, e.g. Business table, and those details wouldn’t be in the hook’s payload by default, so we need to add them.
Okay, maybe it was just the example I saw that didn’t step through multiple tables.
Either way, this fix should be released in the next few minutes (if not already).
If you still run into the issue this evening, please let us know.
Thanks very much for the quick fix @darragh 
