Slack Trigger configuration in N8N self-host

Can’t configure slack trigger node in my selfhost N8N acc. N8N document says it needs OAuth2 API but slack trigger node only support “Slack API”. When I try to connect with Slack API, I got the credential but can’t verify in event subscriptions.

1 Like

Yes, I did all that step but still not working. can’t verify the event subscription.

Thank you for your help brother

1 Like

I am stuck in this step. Now i am trying to figure it out asking N8N assistant from N8N cloud acc. It says “if you are self-hosting or using a tunnel (like Cloudflare), ensure that Slack can reach your endpoint without any restrictions.

  • Some users have reported needing to adjust tunnel/firewall rules to allow Slack’s requests through.”.
1 Like

In order to add the event handler, you need to have the trigger running in n8n. At this point you have configured your node with credentials already, so run the node manually and while it is running, copy the url and paste it to the slack event subscription page. Make use to use the correct URL - testing or production, as this is where the events are going to be sent.

2 Likes

Yes I did the way you said but it can’t be verify yet

1 Like

Yea I have the same problem.

Details:

  • Self hosted via railway
  • Slack message node works
  • Permissions has been set properly
  • Correct WEBHOOK_URL has been configured

Despite this when running the execute test event thing on the slack trigger node it doesnt verify in Slack, similar warning as with @Zay_Tun’s event subscription screenshot.

I hope to resolve this soon, thank you and I hope you guys have the answer me and Zay are looking for :grin:

1 Like

If this is self hosted n8n instance I got around the verify issue by doing the following:

  1. Only the production url would verify
  2. I used ngrok and created a static domain. The free version allows you to create one free static domain. You use the domain in your webhook and not localhost:5678.
  3. I set WEBHOOK_URL environment variable to point to the static domain. example value http://287fa539afa7.ngrok-free.app
  4. Used ngrok to expose the static domain: ngrok http --url=287fa539afa7.ngrok-free.app 5678
  5. After restarting n8n to make sure it picks up the environment variable and activating the workflow. I copied the production webhook url and entered it in the Enable Events section in Slack and it will verify the webhook.

Now the only issue I have not slaved is when I trigger the chat bot n8n states:

Cannot read properties of undefined (reading ‘type’)
Error in handling webhook request POST /webhook/193a8146-e447-4e32-a6c0-a7027e0c0b49/webhook: Workflow Webhook Error: Workflow could not be started!

I have triple checked everything but think its still something to do with a locally hosted n8n instance.

Anyway hope this helps others.

P.S. I believe you can also use n8n in tunnel mode which “should” remove the need to use ngrok. To use tunnel mode start n8n like: n8n start –tunnel

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.