Ylem documentation
  • 🗒️General information
    • Introduction to Ylem
    • Quick start guide
    • Release notes
  • 🔬Open-source edition
    • Installation
    • Usage of Apache Kafka
    • Task processing architecture
    • Configuring integrations with .env variables
  • 💡Integrations
    • Connecting an integration
    • Library of integrations
      • Amazon Redshift
      • Apache Kafka
      • APIs
      • Atlassian Jira
      • AWS Lambda
      • AWS RDS
      • AWS S3
      • ClickHouse
      • ElasticSearch
      • E-mail
      • Google Big Query
      • Google Cloud SQL
      • Google Pub/Sub
      • Google Sheets
      • Immuta
      • Incident.io
      • Jenkins
      • Hubspot
      • Microsoft Azure SQL
      • MySQL
      • OpenAI ChatGPT
      • Opsgenie
      • PostgreSQL
      • PlanetScale
      • RabbitMQ
      • Salesforce
      • Slack
      • Snowflake
      • Tableau
      • Twilio. SMS
      • WhatsApp (through Twilio)
    • Initial demo data source
  • 🚡Pipelines
    • Pipeline management
    • Tasks
      • Aggregator
      • API Call
      • Code
      • Condition
      • External trigger
      • Filter
      • For each
      • GPT
      • Merge
      • Notification
      • Query
      • Pipeline runner
      • Processor
      • Transformer
    • Running and scheduling pipelines
    • Library of templates
    • Environment variables
    • Mathematical functions and operations
    • Formatting of messages
  • 📈Statistics and profiling
    • Statistics of runs
    • Slow tasks
  • 📊Metrics
    • Metric management
    • Using previous values of a metric
  • 💼Use cases, patterns, templates, examples
    • Use cases
    • Messaging patterns
      • Datatype Channel
      • Message Dispatcher
      • Messaging Bridge
      • Message Bus
      • Message Filter
      • Message Router
      • Point-to-Point Channel
      • Publish-Subscribe Channel
      • Pull-Push
    • Functional use cases
      • Streaming from Apache Kafka and messaging queues
      • Streaming from APIs
      • Streaming from databases
      • Data orchestration, transformation and processing
      • Usage of Python and Pandas
      • KPI Monitoring
      • OKRs and custom metrics
      • Data Issues & Incidents
      • Reporting
      • Other functional use cases
    • Industry-specific use cases
      • Finance and Payments
      • E-commerce & Logistics
      • Customer Success
      • Security, Risk, and Anti-Fraud
      • Anti-Money Laundering (AML)
  • 🔌API
    • OAuth clients
    • API Reference
  • 👁️‍🗨️Other resources
    • FAQ
    • Our blog on Medium
Powered by GitBook
On this page
  • Authorizing Ylem in private Slack channels
  • Configuring integration for open-source and on-premise versions
  • Step 1. Create Slack Application

Was this helpful?

Edit on GitHub
  1. Integrations
  2. Library of integrations

Slack

PreviousSalesforceNextSnowflake

Last updated 7 months ago

Was this helpful?

Open-source and On-premise editions of Ylem require separate specific configurations for this integration. See

Integration type: Write

Integration with Slack allows you to send messages to various channels including private ones.

Data for the connection:

Please note that you need admin permissions for your Slack organization to authorize Ylem to send messages to it.

Authorizing Ylem in private Slack channels

To publish messages in private groups on Slack, you need to add Ylem (app) into the group first.

To do it, type @Ylem in the group and click on "Invite Them".

Configuring integration for open-source and on-premise versions

If you don't use the cloud version of Ylem but have it installed on your infrastructure under your domain name, you need to create your own Slack OAuth 2.0 application to make this integration work.

Step 1. Create Slack Application

You don't need to distribute your application publically on Slack Marketplace because it belongs to the same workspace you are planning to use it for.

Add the following as Bot Token Scopes:

Slack App also needs a redirect URL to return users to after a successful authorization. Use this one and just replace the domain name with your one that internally proxies the request to ylem_integrations:7337:

https://%%YOUR_DOMAIN_NAME%%/slack/authorize

As soon as the application is ready, you can open its "Settings" and copy your CLIENT_ID and CLIENT_SECRET. These two values you will need to add to your Ylem configuration now.

Step 2. Configure Ylem .env parameters

The following parameters need to be changed on the backend/integrations/.env file:

INTEGRATIONS_SLACK_OAUTH_CLIENT_ID=%%REPLACE_IT_WITH_THE_CLIENT_ID_OF_YOUR_APP%%
INTEGRATIONS_SLACK_OAUTH_CLIENT_SECRET=%%REPLACE_IT_WITH_THE_CLIENT_SECRET_OF_YOUR_APP%%
INTEGRATIONS_SLACK_AFTER_AUTHORIZATION_REDIRECT_URL=https://%%REPLACE_IT_WITH_THE_DOMAIN_NAME_OF_YOUR_YLEM_INSTANCE%%/jira-authorizations/{uuid}/?justConnected

Now you can open https://%%YOUR_YLEM_DOMAIN_NAME%%/slack-authorizations and try to authorize Slack Integration by clicking on the button "Add Slack authorization".

As the first step, you need to go to the and create your own "OAuth 2.0" application.

Additional information about creating and configuring Slack Apps can be found in their .

💡
https://api.slack.com/apps
official documentation
below