Hello,
Im having trouble getting trouble getting the slack trigger node to work, i already tested the credentials with a get channels node and it worked fine.
I haven’t added the oauth redirect URL to my slack app but i’m using n8n cloud so from what i understand it’s not necessary (and i can’t see it when setting up my credentials either way).
I’ve tried “trigger on any event” and “trigger on new message posted to channel”, neither worked.
It looks like your topic is missing some important information. Could you provide the following if applicable.
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
Using n8n Cloud doesn’t remove the necessity for setting up redirect URLs, as far as I’m concerned.
But I could be wrong.
Open your trigger and check this URL:
Mayba that could be your redirect URL.
i did try that, it didn’t fix it. i tried both with the test URL and production URL
I’ve just created a Slack trigger myself to understand how it works.
It’s quite complex. No wonder you are having a hard time.
Luckly I could find a very detailed YouTube tutorial for you:
How To Connect Slack To N8N
Try to follow the steps of that video and see if this solves your problem.
If it does, please remember to mark this reply as a solution 
Good luck! Let me know how it goes.
The thing is you can see around minute 2 when he’s creating the credentials that he can see the oauth redirect URL, but that doesn’t shouw up in the cloud version.
I’ve seen people say on other topics that cloud n8n handles that connection automatically, i don’t know if it’s true since i didn’t see anything about that in the documentation (i might have just missed it) but either way it’s not working for me and i don’t see what else i can try without that redirect URL 
I know it may sound obvious, but is the workflow active?
Some triggers only work with an active workflow.
Sorry for the late answer, the flow was unactive, but i tried activating it and setting the production URL as Redirect URL in the slack app to test the trigger that way and it didn´t work either so it doesn´t seem like that´s the problem.
Hmm I see. Activating the workflow is a big change to this issue.
Maybe try testing a bit more.
Slack is widely used by many n8n users and I bet many people use it on the cloud version. So it shouldn’t be too hard to make it work.
Now that the workflow is active you can check incoming messages in the Executions tab of your workflow.
Hey there so I have the same issue here, my flow is indeed active, I have the prod URL on api.slack… And it runs basically whenever it wants, then it just stops working and the event never comes through on n8n, until I inactivate the workflow and activate it again
