[
https://issues.apache.org/jira/browse/NIFI-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204510#comment-15204510
]
Adam Lamar commented on NIFI-1578:
----------------------------------
[~joewitt] 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.
> Create PutSlack processor
> -------------------------
>
> Key: NIFI-1578
> URL: https://issues.apache.org/jira/browse/NIFI-1578
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Adam Lamar
> Assignee: Adam Lamar
> Fix For: 0.7.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
