We’re going to use bot and app tokens for this guide.

App-level tokens represent your app across organizations, including installations by all individual users on all workspaces in a given organization and are commonly used for creating websocket connections to your app.Bot tokens are the token type that most apps use. The bot token your app uses will be the same no matter which user performed the installation. Bot tokens are associated with bot users, and are only granted once in a workspace where someone installs the app.There may be several user tokens for a single workspace. User tokens allow you to call API methods on behalf of users after they install or authenticate the app.There are three main token types available to a Slack app: user ( xoxp), bot ( xoxb), and app ( xapp) tokens. When an app is installed, you’ll receive a token that the app can use to call API methods. Slack apps use OAuth to manage access to Slack’s APIs. Look around, add an app icon and description, and then let’s start configuring your app. This page contains an overview of your app in addition to important credentials you’ll need later, like the Signing Secret under the App Credentials header. 💡 We recommend using a workspace where you won’t disrupt real work getting done - you can create a new one for free.Īfter you fill out an app name ( you can change it later) and pick a workspace to install it to, hit the Create App button and you’ll land on your app’s Basic Information page. When you’re finished, you’ll have this ⚡️ Getting Started app to run, modify, and make your own.įirst thing’s first: before you start developing with Bolt, you’ll want to create a Slack app. Along the way, we’ll create a new Slack app, set up your local environment, and develop an app that listens and responds to messages from a Slack workspace. This guide is meant to walk you through getting up and running with a Slack app using Bolt for JavaScript.

Slack app icon