Users should ideally be identified by their unique ID which looks something like 'U011N55HKCL', these IDs can be fetched with the Get Users node. It is however possible to provide the display name in the same way you would identify a user when messaging in the slack app, for example @Person for the user with the display name of 'Person' - the @ must be included to indicate it's a display name and not an ID. Display names are not unique and if multiple users with the same display name are found the node will fail. Please note by providing display names an API call to users.list will be made to enable lookup of the user's unique ID which is a 'Web API Tier 2' method.
To message a group of users the channels:manage scope must be set. Multiple users should be specified as a comma separated list such as U011N55HKCL,U011XEN1RDW. It is possible to mix and match display names and user IDs such as: @Person,U011XEN1RDW. White space will be automatically trimmed.
Notes on username: By default the message will be sent and display with the apps name. If the chat:write:customize scope has been added then it is possible to set a username parameter. If changing the display name / username of the source of the message is desirable then check 'Set username' and provide the username to post the message as. The messages will however appear undo the app regardless of what username is set.
Rate Limiting: The underlying Java Slack API offers an async approach where it attempts to manage Rate Limits on API requests. This node node uses the aysnc version of the method and will send approximately 1 message per second.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.Try NodePit Runner!
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to firstname.lastname@example.org, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.