The Employee Slack Notices Project
This is a 'Project' template which means that it contains a group of workflows that work together to achieve a particular aim
The Employee Slack Notices project is a useful tool for notifying employees of important updates using Slack.
Common Use Cases for Slack AlertsCopy
Notices to sales about prospects
Notices to account managers about customers
Notices to line of business stakeholders about operational updates
Notices to ops teams about technical issues
Workflow DemoCopy
The workflow allows you to quickly build clean Slack messages that are sent as direct message or messages in public channels. You can even embed Salesforce record IDs (e.g., Lead ID, Opportunity ID, Account ID) in the text fields that support markdown and it will replace the IDs with the name and link to that record in Salesforce.
There are some example templates you in the project that you can play with to get an idea of how the workflow works, just run the setup process first, then go to the "[Employee Slack Notices] Example templates" workflow to use the templates.
Here’s a demo video of the workflow using these templates).
How to setupCopy
Read the instructions below to get things setup and/or watch this video walking through the entire setup in less than 10 minutes.
Step 1: Import the Project and open setup workflowCopy
Import the Employee Slack Notices project into your target workspace. Once done, open the "[Employee Slack Notices] Setup & Test" workflow and review the "readme" file in the default branch.
Step 2: Configure the Project Config VariablesCopy
Follow the instructions in the readme file to configure these variables. The project configuration variables are located at the top right of the workflow builder.
You'll need to set/review:
Company name
The bot's avatar (image)
The bot’s username
Your ops channel Slack ID
The base URL for your Salesforce instance (optional)
Step 3: Run the Setup and Test Manual Triggered WorkflowCopy
In the "[Employee Slack Notices] Setup & Test" manually triggered workflow, make sure the "Value To Test" input of the "Setup & Test" branch connector is set to "1".
Before running the workflow, open the workflow used in the "Rebuild the lookup" call workflow connector (called "[Employee Slack Notices] Store public and private Channel IDs in lookup") add your authentication to the Slack connector. The workflow will paginate through every Slack channel in your instance and store them to a table at the account scope using the company name as part of the table name.
Go back to the setup and test workflow and run workflow.
Check the logs of the "[Employee Slack Notices] Store public and private Channel IDs in lookup" workflow to make sure it didn’t fail.
Step 4: Test the Slack Channel LookupCopy
In the "[Employee Slack Notices] Setup & Test" manually triggered workflow, make sure the "Value To Test" input of the "Setup & Test" branch connector is set to "2".
Place a Slack channel name in "Test channel lookup" callable workflow connector and review it’s logs to see if it’s returned a valid channel from your Slack instance.
Step 5: Test a direct messageCopy
In the "[Employee Slack Notices] Setup & Test" manually triggered workflow, make sure the "Value To Test" input of the "Setup & Test" branch connector is set to "3".
Open the "[Employee Slack Notices] Easily send an employee a Slack notification" workflow and add an authentication to the Slack connectors in the workflow.
Go back to the Setup and test workflow and add your email to the "Employee Email" input of the "Test a DM" call workflow connector.
Run the setup and test workflow and check the logs to make sure there’s no failures. You should also get a Slack DM if there were no failures.
Step 6: Test a channel messageCopy
In the "[Employee Slack Notices] Setup & Test" manually triggered workflow, make sure the "Value To Test" input of the "Setup & Test" branch connector is set to "4". Add a Slack channel name to the "Channel Name" input of the "Test a channel message" call workflow connector.
Run the setup and test workflow and check the logs to make sure there’s no failures. You should see a Slack message in the channel you targeted if there were no failures.
Step 7: Embed Salesforce IDs in Your MessagesCopy
If you want to use the feature which embeds the IDs of Salesforce objects in your messages, add an authentication to the Salesforce connectors in both the workflow setup and test workflow and in the "[Employee Slack Notices] Easily send an employee a Slack notification" workflow.
In the Setup and test workflow, add the email of a lead to the email condition of the "Get a lead by email" Salesforce connector.
Add a Slack channel name to the "Channel Name" input of the "Test a channel message" call workflow connector.
Run the workflow to see how the ID is replaced in the Slack message with a link to that record in Salesforce.
Save API Calls with the Employee Directory Project!Copy
If you're using the Employee Directory project, you can save API calls in this workflow (and in many others) by replacing the Slack “get user by email” steps with the employee directory callable lookup. This searches local data storage in Tray vs. making calls to Slack for user IDs, saving you a lot of API calls as you send more and more automated messages.
That's it! You're now ready to start notifying employees of important updates or events using Slack.