You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please note, that this is a legacy custom integration - an outdated way for teams to integrate with Slack. These integrations lack newer features and they will be deprecated and possibly removed in the future. We do not recommend their use. Instead, we suggest that you check out their replacement: Slack apps.
The recommended way to set up a webhook integration with Slack is to use Slack Apps Event API.
This PR aims to report which files and features would be impacted if we decided to migrate to the Slack Apps for setting up webhook integrations.
Setting up webhook integration through the Events API would require guiding the user through creating the new Slack App and setting up Events API.
current doc:
Test Fixtures
Using Events API, we would subscribe to the message.channels event to replicate the current behavior of the legacy Outgoing Webhook. The new payload provides similar data but is in a different format from the current test fixtures.
While the legacy outgoing webhook only worked for public channels, the Events API supports extensive options such as sending messages from DMs, private channels, and also payload from dozens of other event types. Adding support for the newer features from Events API would require adding more test fixtures
馃搫 Overview
Currently, our Slack integration uses the outdated 'Outgoing WebHooks' custom integration feature to configure the webhook integration.
from Slacks' Outgoing Webhooks page:
The recommended way to set up a webhook integration with Slack is to use Slack Apps Event API.
This PR aims to report which files and features would be impacted if we decided to migrate to the Slack Apps for setting up webhook integrations.
Relevant links:
Migrating from legacy integrations
CZO thread: here
Documentation
Setting up webhook integration through the Events API would require guiding the user through creating the new Slack App and setting up Events API.
current doc:
Test Fixtures
Using Events API, we would subscribe to the
message.channels
event to replicate the current behavior of the legacy Outgoing Webhook. The new payload provides similar data but is in a different format from the current test fixtures.While the legacy outgoing webhook only worked for public channels, the Events API supports extensive options such as sending messages from DMs, private channels, and also payload from dozens of other event types. Adding support for the newer features from Events API would require adding more test fixtures
current test fixture for a message:
the same payload from Events API:
The text was updated successfully, but these errors were encountered: