[jira] [Commented] (NIFI-1578) Create PutSlack processor

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229633#comment-15229633 ] 

ASF GitHub Bot commented on NIFI-1578:
--------------------------------------

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. 


> 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)