Replace the heroku-app placeholder with the actual name of your Heroku app. Open up your App Manifest and find the two lines that identify your Heroku endpoint: Now that we have a production version of the app available, we’ll need to make one more change to our Slack configuration to unite the two. Next, go to, and you should see your brand new app listed there. Navigate to Manage Connected Apps, and you should see an app titled “Connected App For Slack.” This is the Salesforce platform policy that the Starter Kit created for your Slack app. First, run the following command in your terminal window: In order to verify that the application was configured and deployed, you can perform two separate steps. If you receive a failure about a missing public key or permissions when pushing to Heroku, run heroku keys:add.Īfter some time, you’ll receive the following message:ĭone deploying Heroku app sfdc-contact-editor Note: if you receive a failure about a missing OrgCreateCommand, make sure you have enabled Dev Hub.
It creates a brand new scratch org and a new Heroku app, and it defines some essential environment variables for the deployed app to use. Now, grab a beverage and sit back, as the Starter Kit sets up some accounts for you.
For the Slack Bot Token, go to the OAuth & Permissions page in your Slack App overview, and copy-paste the Bot User OAuth Token into the terminal.Make sure to select a unique name for your Heroku App, since app names need to be unique across all Heroku apps. For the Heroku App Name, we’ll use sfdc-contact-editor.You’ll be asked to provide some information: Then, run node scripts/deploy.js, and a CLI prompt will take over. First, make sure you’re authenticated to your Salesforce Dev Hub by running sfdx auth:web:login. Setting up a project structure that favors convention over configuration.Using Bolt to abstract away details with authentication.Setting up and deploying a sample application to Heroku.The primary goal of the Starter Kit is to get your environment set up for building, testing, and deploying a Slack App that integrates with Salesforce. With the Salesforce Starter Kit available and its dependencies installed, it’s time to take a look at what the Starter Kit can do. Walking through the Salesforce Starter Kit
Install the dependencies there with npm install then pop up a folder, and install those dependencies: Next, clone the Slack Starter Kit, and then navigate to the scripts directory: If you get an error about a URL being unverified, don’t worry-we’ll address that soon! Paste the following YAML into that box, overwriting what was there by default:ĭescription: shows Salesforce org detailsĬlick Save Changes. Your App Manifest defines some metadata about your app, such as the permissions it requests and the events it handles. On the left side nav bar, click on App Manifest. We’ll be referring to these in the next section. That’s it! If you scroll down, you’ll see your App Credentials.
In this first post, we’ll go through the SDK and set up your development environment for future work! Prerequisitesīefore we begin, make sure you have the following software installed on your machine:
In this series of posts, we’ll show you how to use the Slack Starter Kit and Bolt to create an application that allows users to view and change Salesforce records-entirely in Slack.īy the end of this series, we’ll have a fully functional Slack app that communicates with the Salesforce platform. It’s an opinionated scaffolding framework designed to make it easy to build Slack Apps that integrate with Salesforce data. Taking into account Bolt’s development principles and tooling, they developed the Slack Starter Kit. The folks at Salesforce have done one better.