Chapter 66. Slack Source


Receive messages from a Slack channel.

66.1. Configuration Options

The following table summarizes the configuration options available for the slack-source Kamelet:

PropertyNameDescriptionTypeDefaultExample

channel *

Channel

The Slack channel to receive messages from

string

 

"#myroom"

token *

Token

The token to access Slack. A Slack app is needed. This app needs to have channels:history and channels:read permissions. The Bot User OAuth Access Token is the kind of token needed.

string

  
Note

Fields marked with an asterisk (*) are mandatory.

66.2. Dependencies

At runtime, the slack-source Kamelet relies upon the presence of the following dependencies:

  • camel:kamelet
  • camel:slack
  • camel:jackson

66.3. Usage

This section describes how you can use the slack-source.

66.3.1. Knative Source

You can use the slack-source Kamelet as a Knative source by binding it to a Knative object.

slack-source-binding.yaml

apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: slack-source-binding
spec:
  source:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: slack-source
    properties:
      channel: "#myroom"
      token: "The Token"
  sink:
    ref:
      kind: Channel
      apiVersion: messaging.knative.dev/v1
      name: mychannel

66.3.1.1. Prerequisite

Make sure you have "Red Hat Integration - Camel K" installed into the OpenShift cluster you’re connected to.

66.3.1.2. Procedure for using the cluster CLI

  1. Save the slack-source-binding.yaml file to your local drive, and then edit it as needed for your configuration.
  2. Run the source by using the following command:

    oc apply -f slack-source-binding.yaml

66.3.1.3. Procedure for using the Kamel CLI

Configure and run the source by using the following command:

kamel bind slack-source -p "source.channel=#myroom" -p "source.token=The Token" channel:mychannel

This command creates the KameletBinding in the current namespace on the cluster.

66.3.2. Kafka Source

You can use the slack-source Kamelet as a Kafka source by binding it to a Kafka topic.

slack-source-binding.yaml

apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: slack-source-binding
spec:
  source:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: slack-source
    properties:
      channel: "#myroom"
      token: "The Token"
  sink:
    ref:
      kind: KafkaTopic
      apiVersion: kafka.strimzi.io/v1beta1
      name: my-topic

66.3.2.1. Prerequisites

Ensure that you’ve installed the AMQ Streams operator in your OpenShift cluster and created a topic named my-topic in the current namespace. Make also sure you have "Red Hat Integration - Camel K" installed into the OpenShift cluster you’re connected to.

66.3.2.2. Procedure for using the cluster CLI

  1. Save the slack-source-binding.yaml file to your local drive, and then edit it as needed for your configuration.
  2. Run the source by using the following command:

    oc apply -f slack-source-binding.yaml

66.3.2.3. Procedure for using the Kamel CLI

Configure and run the source by using the following command:

kamel bind slack-source -p "source.channel=#myroom" -p "source.token=The Token" kafka.strimzi.io/v1beta1:KafkaTopic:my-topic

This command creates the KameletBinding in the current namespace on the cluster.

66.4. Kamelet source file

https://github.com/openshift-integration/kamelet-catalog/slack-source.kamelet.yaml

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.