Taragolis commented on PR #26374: URL: https://github.com/apache/airflow/pull/26374#issuecomment-1247796063
Right now there are 3 ways to send formatted message to slack 1. Use [Slack API](https://api.slack.com/) and [chat.postMessage](https://api.slack.com/methods/chat.postMessage). Supported by [Python Slack SDK](https://slack.dev/python-slack-sdk/web/index.html) 2. Use [Slack Incoming Webhook](https://api.slack.com/messaging/webhooks) based on Slack App. Supported by [Python Slack SDK](https://slack.dev/python-slack-sdk/webhook/index.html) 3. Use [Incoming Webhook based on Slack Integration](https://taragolisworkspace.slack.com/apps/A0F7XDUAZ-incoming-webhooks?tab=more_info). Slack integration itself is [legacy tech](https://api.slack.com/legacy/custom-integrations) for a while. And only Slack API use for [other integration](https://api.slack.com/methods) with slack. **Authentification** Slack API use [access token](https://api.slack.com/authentication/token-types) based on the type of integration (e.g. for Bots `xoxb-1234567890123-09876543210987-AbCdEfGhIjKlMnOpQrStUvWx`) and send requests to `https://www.slack.com/api/` (by default) Slack Incoming Webhook and Incoming Webhook based on Slack Integration use URL (the same format: `https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX`) for auth. The main differences between Slack Incoming Webhook and Legacy version that for legacy integration you could change `username`, `channel`, `icon_url` and `icon_link`. If you tried to send this parameters to Slack Incoming Webhook it just ignored and user wouldn't notified. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
