Sample app to showcase Slack + Salesforce integrations.

This app has been created using the Salesforce Slack Starter Kit. For a detailed explanation of the app architecture and the scaffolding script, take a look at Salesforce Slack Starter Kit's README.

To be able to run this project you will need:

• git (download here)
• node >= 14 (download here)
• Salesforce Developer Org
  • If you don't have one, sign up for a free Developer Edition org or a Trailhead Playground.
  • If you want to use scratch orgs follow the instructions to enable Dev Hub in your Salesforce Developer Org.
• sfdx CLI >= sfdx-cli/7.129.0 (download here)
• Heroku account (signup)
• heroku CLI (download here)
• Slack Workspace
  • If you don't have one, create one.

1. Open https://api.slack.com/apps/new and choose From an app manifest
2. Choose the workspace you want to install the application to
3. Copy the contents of manifest.yml into the text box that says Paste your manifest code here and click Next
4. Review the configuration and click Create
5. In Basic Information scroll down to the Display Information section. Upload a picture for the app. You can use this logo
6. Now click Install App on the left menu. Then click the Install to Workspace button and then click on Allow

1. Authenticate to your Salesforce org and set as default:

sfdx auth:web:login --setdefaultusername -a mydevorg

2. Login to your Heroku Account

heroku login

3. Clone the ready-to-fly repository

git clone https://github.com/trailheadapps/ready-to-fly

4. Run Deployment Script

cd ready-to-fly/scripts
npm install
cd ..
node scripts/deploy.js

5. Choose Non-Scratch Org when the script prompts you to select Salesforce environment

6. The script prompts you to enter value for SLACK_BOT_TOKEN. To enter this value open your apps configuration page from this list, click OAuth & Permissions in the left hand menu, then copy the value in Bot User OAuth Token and paste into terminal.

7. The script prompts you for slack signing secret SLACK_SIGNING_SECRET. To enter this value open your apps configuration page from this list, click Basic Information and scroll to the section App Credentials and click show button and copy the Signing Secret and paste into terminal.

1. Authenticate to your Salesforce org that has DevHub enabled

sfdx auth:web:login --setdefaultdevhubusername -a DevHub

2. Login to your Heroku Account

heroku login

3. Clone the ready-to-fly repository

git clone https://github.com/trailheadapps/ready-to-fly

4. Run Deployment Script

cd ready-to-fly/scripts
npm install
cd ..
node scripts/deploy.js

5. Choose Scratch Org when the script prompts you to select Salesforce environment

6. The script prompts you to enter value for SLACK_BOT_TOKEN. To enter this value open your apps configuration page from this list, click OAuth & Permissions in the left hand menu, then copy the value in Bot User OAuth Token and paste into terminal.

7. The script prompts you for slack signing secret SLACK_SIGNING_SECRET. To enter this value open your apps configuration page from this list, click Basic Information and scroll to the section App Credentials and click show button and copy the Signing Secret and paste into terminal.

Note: As ready to fly performs calls from Salesforce to Slack, we've modified the Salesforce Slack Starter Kit script to deploy a remote site setting and a custom metadata type record used for callouts. We've also included the setup of some sample data.

This is the final step, you will need to enter the current Heroku Instance url in Slack App.

1. To enter this value open your apps configuration page from this list, click App Manifest. Find the request_url fields (there will be two to update) in the manifest and modify it to replace heroku-app with your actual heroku domain name. Note at the end of this step your url should look like https://<heroku-domain>.herokuapp.com/slack/events.
2. Once done that, you'll be prompted to verify the events endpoint. Click on 'verify'. You're ready to navigate to the app home!

• For Salesforce metadata synchronization use sfdx force:source:pull to retrieve and sfdx force:source:push to deploy metadata from orgs to local project folder force-app

• For Salesforce metadata synchronization in developer orgs use sfdx force:source:retrieve -p force-app/main/default to retrieve and sfdx force:source:deploy -p force-app/main/default to deploy metadata from orgs to local project folder force-app

• For the Bolt Node.js app use the steps below:
  • cd into apps/ready-to-fly folder cd apps/ready-to-fly
  • add git remote to app repo using heroku git:remote -a <heroku app name>
  • run git push heroku main to push code to Heroku

1. To use ngrok, first install it downloading the executable or with npm:

$ npm install ngrok -g

2. Next you’ll have to sign up.
3. Once logged in, navigate to “Setup & Installation“ and copy your auth token.
4. Then set your auth token in your local machine:

$ ngrok authtoken my_auth_token

5. Run the ngrok tunnel as follows:

$ ngrok http 3000

6. Copy the ngrok tunnel URL to the following places:

• Your manifest file request URLs
• The HEROKU_URL environment variable in your .env file
• The Callback URL for the connected app that’s used for authorization in Salesforce - simply add the ngrok URL in a new line
• Add a new remote site setting that contains the ngrok URL, as it’s the one that we’ll use to callout from Salesforce to Slack
• Modify the BoltAppConfigHeroku custom metadata type record URL__c, as it’s used in the Apex logic to make the callout

7. Now you are prepared to run the app locally! In another terminal different from the one in which you’re running ngrok, execute node app.js from the project folder. You can then make changes to the code and restart the app as many times as you want.

The Managers dropdown that appears when you create a travel request is populated with information pulled from Salesforce. Concretely, we look at the standard Manager field on the User object and pull two levels of Managers in the hirerachy. You can change that behavior to adapt it to your needs.