Github user adamonduty commented on the pull request:
https://github.com/apache/nifi/pull/256#issuecomment-206686328
@joewitt I'm only now just realizing that my reply to your comment was in
the wrong place. Here's my reply which I originally made on the JIRA:
==============
My use case around PutSlack at this point is pretty simple. Basically the
same use cases around PutEmail, but sending to a Slack channel instead of an
email distribution list. This allows teams to keep an eye on their dataflows in
a natural place, especially since many other Slack integrations exist (Jenkins,
github, etc).
To configure PutSlack, a Slack user (or maybe admin) has to add the
Incoming Webhooks integration to the Slack team, then add a webhook to a
specific channel. Once the user has the URL associated with this webhook, they
drop the URL into PutSlack along with a webhook text template.
Does that help? The use cases would probably also increase with a GetSlack
processor, which when paired with PutSlack could allow one to manually trigger
flows in NiFi via a chat bot.
==============
Also, just to be clear, the Travis build above failed on JDK8 due to an out
of memory exception unrelated to PutSlack.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
