Changes between Version 3 and Version 4 of study Slack functionalities


Ignore:
Timestamp:
Nov 6, 2018, 2:35:46 PM (7 years ago)
Author:
xsabol
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • study Slack functionalities

    v3 v4  
    11**Documentation**
    2 Range of chatbot's functonality depends on scopes (or in other words, list of API calls chatbot is allowed to use). These can be set in [https://api.slack.com/] for your app in OAuth & Permissions tab. The *.history call is currently the most important one as it is responsible for collecting history of channels
     2
     3Range of chatbot's functonality depends on scopes (or in other words, list of API calls chatbot is allowed to use). These can be set in [https://api.slack.com/] for your app in OAuth & Permissions tab. These scopes automatically apply (after admin's confirmation) to your bot and user tokens which are used in source:constants.py. The *.history call is currently the most important one as it is responsible for collecting history of channels.
     4
    35Scopes for .history API call:
    4 * channels.history: collects history only from SLACK public channels
    5 * groups.history: same as with channels, but this one works only for private channels
    6 * im.history: collects chat history from private conversations
    7 * mpim.history: collects chat history from multi-party conversations
    8 * [https://api.slack.com/methods/conversations.history|conversations.history]: universal scope for all 4 API calls mentioned above, it's functionality depends on which of those 4 scopes is chatbot allowed to use. For example: if chatbot is allowed to view groups and channels but not allowed to view private messages and multi-party conversations, those API-calls get rejected automatically without limiting other scopes
     6* [[https://api.slack.com/methods/channels.history|channels.history]]: collects history only from SLACK public channels
     7* [[https://api.slack.com/methods/groups.history|groups.history]]: same as with channels, but this one works only for private channels
     8* [[https://api.slack.com/methods/im.history|im.history]]: collects chat history from private conversations
     9* [[https://api.slack.com/methods/mpim.history|mpim.history]]: collects chat history from multi-party conversations
     10* [[https://api.slack.com/methods/conversations.history|conversations.history]]: universal scope for all 4 API calls mentioned above, it's functionality depends on which of those 4 scopes is chatbot allowed to use. For example: if chatbot is allowed to view groups and channels but not allowed to view private messages and multi-party conversations, those API-calls get rejected automatically without limiting other scope
     11
     12I am currently using conversations.history. That allows users to set up the app using any combination of these 4 permissions (it obviously needs to have 1 or more) limiting the bot's functionality to certain types of channels.
    913
    1014List of potentionally useful information that can be obtained with SLACK API calls: