Sorry, not sure if that is correct way of creating the post with the link.
I got stuck on step7.
Looks like my “success” page is slightly different than your with the green “reinstall” button.
I assume it has something to do with the need for admin of the space to authorise my app?
Hello @Won_t_Tell, yes, apparently, the administrator has configured the workspace to always ask for approval before any new App is installed.
However, this tutorial was initially built because there was some issues when users were trying to add the default Make “Slack/Watch New Events”. Now, it’s solved, and, if you want to start a scenario when someone types a message in a specific channel, you can try and use this module, without installing any app in Slack.
Kind regards
Hi
Thank you.
I have tried it but it didnt trigger “Immedietely” (it wasnt an option".
The shortest I could set up was 15 mins.
I am building company knowledge database and need instant message discovery?
Will this integration allow for instant trigger?
Tom
@Won_t_Tell This module is tagged as “Instant”, which means it’s what we call an “Instant Trigger”. When you add one, it should make you create a new Webhook. And then, you should be able to select “Immediately as data arrives” for the scheduling type.
Can you please do a screenshot and show your configuration?
Hey,
I have set up one from scratch. I have been using “Watch Private Channel Messages” before.
So this is my new set up.
However I only managed to trigger it once with and the outcome is seen there.
Then I typed few separate lines in slack by they are not picked either by “Run this module once”, “Run once” or green check (Immediately as data arrives).
@Won_t_Tell normally, there is a defect if you use an “older” connection for Slack.
May I ask you to delete this scenario, create a new one, and when you are asked to select the connection (when configuring the webhook), you click Add and create a brand new connection to Slack?
Then configure the channel, etc. And test again?
Ben
I have created brand new webhook, channel and connection.
I started with posting first message on slack, then in make.com, while “Immediately as data arrives” off I pressed “Run once” and then in the pop up (“Unprocessed data in the webhook”) → use existing data.
It processed every message.
the moment I toggled on “Immedately…” it stops working - message from slack is not picked up, “Run once” button does not trigger anything but red “Stop” button there in the corner.
Only when I toggle off, post the message and click Run Once it will trigger.
@Won_t_Tell just set your scenario to off, then to on, and click “delete old messages”.
If your scenario is ON, clicking “run once” will allow you to “capture” the new message so that you directly see the scenario picking it.
If you scenario is OFF, clicking “run once” will allow you to capture a new message, but if there is a new message in Slack, it will go in the queue of the webhook. And then, when you click “Run Once” again, it will show the pop-up you have. If you select “Use existing data”, it will pick the next message in the webhook queue. If there are other messages, it will ask you again the next time you run, until you empty the webhook queue.
That’s why it could simpler that you set your scenario off then on, delete old messages, and then you exit the scenario builder and go to “Diagram”. As soon as you type a message in Slack, you should see an execution trigger in Make.
I hope I was clear 
ok, I had similar problems with other webhooks (for example Telegram).
Now I got it (not fully yet, hehe but on/off, deleting and going to the diagram works).
I have been all the time in the edit mode, checking all from there so there was a mess.
Now I will make sure I follow the logic you explained and go back to Diagram,
I will test it now with my telegram bot. Thank you
1 Like
I’m happy it works now.
Personally, I often leave the scenario off and use run once, especially when I debug.
But sometimes, if I forget to do run once, it gets messy as well 
1 Like