ListenSlack

ListenSlack 2.0.0

Bundle: org.apache.nifi | nifi-slack-nar
Description: Retrieves real-time messages or Slack commands from one or more Slack conversations. The messages are written out in JSON format. Note that this Processor should be used to obtain real-time messages and commands from Slack and does not provide a mechanism for obtaining historical messages. The ConsumeSlack Processor should be used for an initial load of messages from a channel. See Usage / Additional Details for more information about how to configure this Processor and enable it to retrieve messages and commands from Slack.
Tags: command, event, listen, message, real-time, receive, slack, social media, team, text, unstructured
Input Requirement: FORBIDDEN
Supports Sensitive Dynamic Properties: false

Properties

App Token
The Application Token that is registered to your Slack application

Display Name

App Token

Description

The Application Token that is registered to your Slack application

API Name

App Token

Expression Language Scope

Not Supported

Sensitive

true

Required

true
Bot Token
The Bot Token that is registered to your Slack application

Display Name

Bot Token

Description

The Bot Token that is registered to your Slack application

API Name

Bot Token

Expression Language Scope

Not Supported

Sensitive

true

Required

true
Event Type to Receive
Specifies the type of Event that the Processor should respond to
Display Name

Event Type to Receive

Description

Specifies the type of Event that the Processor should respond to

API Name

Event Type to Receive

Default Value

Receive App Mention Events

Allowable Values
- Receive App Mention Events
- Receive Message Events
- Receive Commands
- Receive Joined Channel Events
Expression Language Scope

Not Supported

Sensitive

false

Required

true
Resolve User Details
Specifies whether the Processor should lookup details about the Slack User who sent the received message. If true, the output JSON will contain an additional field named 'userDetails'. The 'user' field will still contain the ID of the user. In order to enable this capability, the Bot Token must be granted the 'users:read' and optionally the 'users.profile:read' Bot Token Scope. If the rate limit is exceeded when retrieving this information, the received message will be rejected and must be re-delivered.
Display Name

Resolve User Details

Description

Specifies whether the Processor should lookup details about the Slack User who sent the received message. If true, the output JSON will contain an additional field named 'userDetails'. The 'user' field will still contain the ID of the user. In order to enable this capability, the Bot Token must be granted the 'users:read' and optionally the 'users.profile:read' Bot Token Scope. If the rate limit is exceeded when retrieving this information, the received message will be rejected and must be re-delivered.

API Name

Resolve User Details

Default Value

false

Allowable Values
- true
- false
Expression Language Scope

Not Supported

Sensitive

false

Required

true

Dependencies
- Event Type to Receive is set to any of [Receive Joined Channel Events, Receive App Mention Events, Receive Message Events]

Relationships

Name	Description
success	All FlowFiles that are created will be sent to this Relationship.

Writes Attributes

Name	Description
mime.type	Set to application/json, as the output will always be in JSON format