![]() ![]() ![]() There are also dozens of other event types available for subscription, and for your app to react to. Using channel will help replicate the first outgoing Webhook feature, and looking for the trigger words in the text string will replicate the second.Įven better, while Outgoing Webhooks only worked for public channels, the Events API can be used with private channels, direct message conversations, or multi-party direct message conversations. When an app receives that data payload, it'll be able to see both the source channel and the text of the posted message. This will push a data payload to an app every time a message is posted to a public channel. ![]() The Events API can be used to replace this by subscribing to the message.channels event type. If you previously created any outgoing Webhooks using legacy integrations, you should switch to a Slack app and replicate the functionality using the Events API. If you were using outgoing webhooks to provide a bot-like behavior with your legacy integration, you might be interested in reading our Enabling Interactions with Bots guide which explains more specifically how the Events API can be used to enable a conversational interface with a Slack app. Our guide to the Events API will walk you through the process of enabling this functionality in a Slack app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |