Unable to connect Slack Trigger ( Request URL not verifiable)

Hi,

I am having difficulty connecting the slack trigger in my n8n workflow. I have reviewed numerous other concerns on the this issue ( request URL not verified). Some post/thread have indicated that the work for needs to be active –if using the prod URL. I have also seen others saying to “watch the entire channel”. And others have mentioned that the the test url does not work for them only the prod url works. Others have mentioned that they would copy & paste the test or prod url, then go back to the workflow and execute it, then return to “retry” the request url for it to be verified. I have watched countless youtube videos following the exact same sequence I have tried and yet the [request url] on slack is never verified. Aside from so many people having the same issue, almost every post suggests a different process to resolve the issue. None of those have worked for me. a select few ( from what I have researched ) have actually resolved it, none of those solutions are relatively recent.

The n8n platform has changed a bit in slight places. For example, the (active/inactive) workflow is now (publish/un-publish). I am seeking a solution that actually works.

Is there proper process solve this problem? The issue being connecting slack to my workflow where I can get the request URL verified under the Event Subscriptions > Enable Events

What is the error message (if any)?

Request URL : Your URL didn't respond with the value of the challenge parameter.

Please let us know if you’re running n8n in the cloud or self-hosted. Also, which version are you running?

If you’re in the cloud, just follow the instructions linked below and make sure that your either using the test URL and the “Execute Workflow” in the editor during testing, or the production URL and publish your workflow prior to this. When running in production with production URL, you cannot use the “Execute Workflow” function in the editor anymore.

If you’re running n8n self-hosted make sure that you’re using it with a valid domain and reverse proxy setup like cloudflare tunnel, ngrok or similar.

I am running n8n in the cloud. I will give it a try