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
I have not been able to get the workflow working that I wanted. Essentially was looking to create an AI-powered Slack bot that can go into a Google Sheet and retrieve only the information they asked for, and then update information when necessary without them having to touch the spreadsheet.
I know how to set up the workflow but my issue is getting slack to cooperate with the workflow. I have tried this same workflow numerous times. As of right not I am having 2 issues. I have 2 workflows set up.
Workflow A: Slack → AI Agent → Model → Call n8n Subwork flow → Slack
Workflow B: Subwork flow( when executed by another workflow) → Google Sheets → filter
I tested by executing WF(B) and it outputs the data in the Google sheets
I tested WB(A) by typing something in the chat attempting to retrieve data from the google sheet in WF(B) and I get an error, stating that its not able to retrieve the data. When I directly connect the google sheet to WF(A) everything works as expected. The only issue with this ( direct connection) is that the input for the filter would be incorrect becuase it would not be coming from ( When exected by another workflow).
The second issue is not being able to get slack verified. for some reason the request URL that you copy and paste to the Event Subscription has be declining the connection.
Yes both workflows are published (or active). Work in the cloud version not local.
It would be great to connect with anyone who understands what am trying to do, or anyone who has already completed this task, or something similar.
Thanks in advance
Dear @Sherlock_nd ,
sorry for the late reply! Lets connect for a quick call to see if I can help you in a one on one session.
I will send you a DM about this.
Have you been able to solve this ? I also have the same issue and have not been able to fix it. Please help 
@Sherlock_nd @salmansolutions
@Atharva_Dastenavar
The only supported way to connect Slack Events in n8n Cloud is:
- Use the Slack Trigger node
- Use the Production URL
- Publish the workflow
Nothing else will work reliably.
@Atharva_Dastenavar No I have not figured this out. Its been an ongoing challenge.
@tamy.santos Have you tried to do this lately? These steps you have mentioned I have tried and aware of. The concern is that the Prod URL is not verified when pasted into the request url for slack. I do see the difficulty in this step. But for some reason its not working for me.
Hey, @Sherlock_nd !
Yes, I’ve done this recently and those steps are still the correct baseline, but there are a couple of details that usually make the difference.
Make sure you are copying the Production Webhook URL from the Slack Trigger (not the test URL), pasting it into Slack’s Event Subscriptions > Request URL, and that the workflow is already published/active when you click save in Slack. Slack only accepts one Request URL per app, so if that field was previously pointing to any other URL (test URL, old workflow, different instance), the verification will fail.
If it still doesn’t verify, the issue is usually outside n8n (like a proxy, tunnel, or firewall altering the request), so double-check those network layers and, if possible, share screenshots of your Slack Event Subscriptions and Slack Trigger config so it’s easier to spot what’s blocking the verification.
@tamy.santos I will give this another test run this week. The steps you have mentioned above are the same I have done on multiple occasions. This issues only worked for me the very first time I was testing it out months ago. But when I revisited this again sometime later I was running into these issues I mentioned in my post.
Let me give it another try. Hopefully it’ll work this time
@Sherlock_nd
Thanks for checking again and for the context, that’s really helpful.
Totally fine, sometimes things behave differently when we come back to them after a while. Give it another try this week and let me know how it goes. If it still doesn’t work as expected, we can take another look together.
Fingers crossed it works this time 