Ok so it must be going wrong when it tries to get the list of channels to get the ID.
I’ve added a new option to the send message nodes which let you bypass the conversation lookup and pass in the channel name directly (though the API docs suggest not using channel names directly).
It should be building in the nightly build shortly and will be version 2.5.0. You’ll need to get this from the nightly/trunk update site.
The updated version looks like this:
Can you try running it with Lookup conversation unchecked please?
It might be a little while before the update makes it into the update site.
Are you using the zip due to an issue with a company firewall/proxy? I’ve not checked the zip but it should be the same contents as the live version.
Can you provide a screenshot of what the update size from the zip looks like when browsing from in KNIME?
The Slack integration should be under “KNIME Community Extensions (nightly build) - Other” and it’s the last entry in the list.
You could try unchecking “Hide items that are already installed” but this would only hide the Slack integration if you had that version or a newer one already installed. I bumped the version number to 2.5.0 so you shouldn’t have been able to have a newer version already.
Yes as we need to upgrade to 4.2 version with this change. Hence, I am testing on my local m/c but I don’t see slack nodes while loading this zip file.
Theres nothing 4.2 specific I can make the change work for 4.1 also if it doesn’t just install anyway already.
Did you try the things I asked in the last post? I’d like to find out if it’s missing or if KNIME thinks you have that or a newer version already. Unchecking hide items already installed will reveal that.
Well, I could able to install on my local m/c but I am getting same error (Provided channel name is not valid) with or w/o opting Lookup conversion. I don’t even see the channel under Get Channel request
Oh I see. I didn’t make a change to how the channels are fetched so still not seeing it there is expected.
I took another look at the code to check to see if I’d forgotten something. Turns out although I have updated the node to pass the channel name directly when you uncheck the Lookup conversation the node still runs the pre-check for whether the channel exists and this pre-check doesn’t think your bot is in that channel (or your this channel > channel number 1000 in your workspace).
I’ve corrected this and it’s building now. Sorry for the mistake it’s tricky to write tests for this as I can’t recreate it locally. Will hopefully be available within half an hour or so, the zip filename will have changed so you will have to look for the latest version under nightly builds from https://www.knime.com/community
The slack nodes will be version 2.5.1.timestamp when it’s build.
If you are on 2.5.1 and are seeing the ‘channel_not_found’ issue then I’m afraid the problem most likely lies with your slack bot setup and not the nodes. Why it would work in the tester API and not the node if you are using the exact same token I don’t know.
If you aren’t on 2.5.1 can you try updating it again?
Ok great, I’ll push the change out to the release versions.
Is it likely you have more than 1000 channels in your Slack workspace? That’s the only reason I’ve found so far that explains why the original approach won’t work.
It is now available in both the 4.1 and 4.2 trusted sites.
Though if you need the zip files it looks like you may have to wait until tomorrow as it doesn’t look like the zip file gets updated when I trigger a build like the live versions do. I’m not sure what the folks at KNIME set up for this. This might be why you couldn’t see it in the zip you downloaded it but I could install it from the live trunk url.
