![]() It sounds like all the steps you've outlined are correct-once the user completes the oAuth process you can save all the associated information locally and use it for connecting to the API. ![]() Also it there any best practise guide you would recommend me to read before finalising my Bot? What all data needs to be saved to keep the bot alive for any channel? I mean we get most of the data from Slack api so I guess bot token and user_id is what is essential part of this. So that I could send and receive data and save it for him. ![]() If that's successful I will save this user slack ID along with his bot_tokens so that I can communicate with him and associate this his slack_user_id with my application user_id.Then i'll authenticate this user to slack by sending the code, client_id and client_secret and redirect_uri. At the top right of the page, click Approve next to Manage app for entire workspace and approve PagerDuty app changes.I'll get code and state from slack which I'll send to back end along with the the user email id and other details of that user associated to my application.I am making the user login to my web app where the user will hit "Add to Slack" button and then One quick question for which would help me architect my bot correctly. Here's my query and response from Slack support Slack Bot Tutorial: Guide to Create Best Slack Bot for Workspace By Ishan Gaba Last updated on 1781 Table of Contents With remote working becoming the predominant way of doing things after the coronavirus pandemic, Slack has become a widely used communication tool. Check out the scope documentation for more detail. take place on the Enterprise Grid org, not on an individual workspace, using the workspace switcher during the install flow. I was pleased with their quick reply and also to know that I was doing it right way. The OAuth installation must: be initiated by an Enterprise Grid admin or owner. For example, you can automate the creation. So I emailed this query to Slack support. Using the Slack connector, you can subscribe to workspace-level events and manage channels, groups, and more. While making this Bot, I was a little curious to know if saving the team credentials in our DB for monitoring and responding back to teams was the right way to mange Slack team credentials. Which can be used to access the concerned workspace to listen and respond back in any added channel or DM. Once the incoming Workspace request in authenticated, Slack API provides us with the team access_tokens. Workspace here means any slack subdomain or a Slack team. Using these, we can authenticate incoming requests to add our Bot to any Slack Workspace. When you make a Slack Bot, Slack provides you with client_id and client_key. 2 min read Managing Slack Workspace Credentials using Slack Bot Secret key and ID Slack is a channel-based messaging platform.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |