Version: 17.07
Supported Since: 17.07
The Slack Egress Connector is used to send messages from ESB to a Slack team using a registered WebHook.
On Exception |
The message will be emitted from this out port if the processing element failed to send the message ot the external system |
Response Processor |
The response message received will be directed to emitted port. You can use this port to connect any processing element or connector that is supposed to process/consume the response. |
Connector Operation |
This port is used to connect operational elements to the Egress Connector. By-default, user does not have to connect any operational element and the default connector operation will be used. |
* marked fields are mandatory
WebHook URL * |
Basic |
Incoming WebHook URL which has been registered with a Channel or a User |
Send to Default Channel/User |
Basic |
Send the message to the default Channel/User where the incoming WebHook was registered with. Default value is false |
Receiver’s Type |
Basic |
Receiver’s type, whether it is a CHANNEL or a USER. Default value is CHANNEL |
Receiver’s ID |
Basic |
Unique identifier of the Channel/User. The value can be a constant or a placeholder expression which contains
|
Message |
Basic |
Message can be a plain text message or any combination placeholder expression such as
|
User Name |
Basic |
Slack user name. If not specified the name assigned to the Incoming WebHook will be displayed when sending messages |
To test the Slack Egress Connector, you need a have a slack team and a registered WebHook URL for a particular channel/user.
In this sample let’s create an integration flow which is able to send Slack messages to a channel named general
.
For that a Timer Ingress Connector is used to generate message contexts and inject to the Slack Egress Connector followed
by a String Payload Setter.
The Integration flow is as shown below