Slack 9.1
Slack is a cloud-based platform that brings all your collaboration and messaging tool needs together, for both individuals and companies.
- On this page
- Slack
- Overview
- API Information
- Templates
OverviewCopy
Slack is a versatile tool for messaging, sharing files, and collaboration within teams. It allows you to create channels for organized communication, react to important events, and configure the platform to suit your team’s unique tech stack. Whether it's integrating with other tools, automating workflows, or simply enhancing team communication, Slack provides a comprehensive environment tailored to your specific needs.
API InformationCopy
The Base URL used for the Slack connector is https://slack.com/api. More information can be found on their main API documentation (v1) site. Details regarding their API limitations can be found here.
TemplatesCopy
These Templates provide pre-configured (best practice) examples of how to work with Slack and integrate it with other services.
PLEASE NOTE: We strongly advise users to read the Authentication and Notes on Using Slack sections to avoid common pitfalls before using any templates. This will help ensure a smooth setup and prevent common errors during integration.
Send Slack alert on workflow failure
Sends a notification to a Slack channel each time a given workflow fails
Slack keyword alert
Monitors Slack channel messages for specific keywords and alerts a dedicated channel
Notify Slack when Salesforce Opportunity is "Closed Won"
Sends a celebratory Slack notification to a chosen channel when an opportunity is successfully closed in Salesforce
Create new hire in Bamboo when 'hired' in Greenhouse
Set up new hires in Bamboo when marked as 'hired' in Greenhouse, and alert the team on Slack
Create Google Account
Automatically creates a G-Suite account for new hires
Create Salesforce accts / opps with Slack modal
Presents users with a referral form in Slack to create a new account / opportunity in Salesforce
Notify Slack with Zendesk ticket info
When a Zendesk ticket is created or updated, send appropriate info to Slack
AuthenticationCopy
Version 10Copy
When using the Slack connector for the first time, you need to create a new authentication.
Name your authentication and specify the type (Personal or Organizational).
The next page optionally asks for User Scope and Slash Command Signing Secret.
User scope: You can set additional permission scopes for users if needed, following Slack's Permission scopes document.
Add only user scopes to this field; adding other scopes will cause authentication failure.
After adding the user scope, ensure that the Use user token field in the Advanced properties section of Slack's properties panel is set to
true. If this is not set totrue, the user scope will not be applied.The
channels:writeuser scope, for example, allows you to send messages as a user rather than as a bot.For a detailed understanding, refer to the User Scope vs. Extra Permission Scopes section.
Slash Command Signing Secret: This is only necessary if you intend to use Slash commands and want an added layer of security. Slash commands can work without signing secrets.
IMPORTANT:
This is not a mandatory part of the authentication process.
This is also not necessary when working with Slash commands.
You only need this field if you require an extra security layer for your a Slash command.
Refer to the Slash Command Signing Secret section for instructions on how to obtain your Slash command signing secret. Feel free to skip this field if it is not needed for your use case.
The next step is to select your service permissions. Basic permissions are pre-selected for your convenience. Feel free to check or uncheck the permissions based on your specific use case.
The last optional field allows you to set additional permission scopes for users, following Slack's Permission scopes document. For a detailed understanding, refer to the User Scope vs. Extra Permission Scopes section.
Do not add user scopes to this field; adding user scopes will cause authentication failure.
Once done, click Create authentication.
In the dialog box, choose the workspace from the top right, and then click Allow.
Return to the authentication field in the workflow builder properties panel, and select the newly created authentication from the available dropdown options. Your connector authentication setup for Slack version 10 is now complete.
Version 9.1Copy
When using the Slack connector for the first time, you need to create a new authentication.
Name your authentication and specify the type ('Personal' or 'Organizational').
The next page optionally asks for the Slash Command Signing Secret.
This is only necessary if you intend to use Slash commands and want an added layer of security. Slash commands can function without signing secrets.
IMPORTANT:
This is not a mandatory part of the authentication process.
This is also not necessary when working with Slash commands.
You only need this field if you require an extra security layer for your a Slash command.
Refer to the Slash Command Signing Secret section for instructions on how to obtain your signing secret. Feel free to skip this field if it is not needed for your use case.
The next step is to select your service permissions. For your convenience note that the basic permissions are already pre-selected. Feel free to check or un-check the permissions based on your use case.
The last field allows you to set additional permission scopes for users if needed, following Slack's Permission scopes document. For a detailed understanding, refer to the User Scope vs. Extra Permission Scopes section.
Do not add user scopes to this field; adding user scopes will cause authentication failure.
Once done, click Create authentication.
In the dialog box, choose the workspace from the top right, and then click Allow.
Go back to your settings authentication field (within the workflow builder properties panel), and select the recently added authentication from the available dropdown options . Your connector authentication setup for Slack's version 9.1 is now complete.
Return to the authentication field in the workflow builder properties panel, and select the newly created authentication from the available dropdown options. Your Slack connector authentication setup for version 9.1 is now complete.
Slash command signing secretCopy
To locate your slash command signing secret:
Go to the Slack API page and click Your apps in the top right corner. On the next page select an app from your available list or create a new one if necessary.
You will be redirected to the Basic Information page of your App. Scroll down to the App Credentials section.
Your Signing Secret (i.e., Slash Command Signing Secret) can be found in this section.
User Scope vs. Extra Permission ScopesCopy
The User Scope field is available from version 10.
Ensure that you create distinct authentications for sending messages as a Bot and as a User.
User scope | Extra permission scopes | |
|---|---|---|
Acceptable scopes | accepts scopes that are relevant to both Users and Users + Bots | accepts scopes athat are relevant to both Bot and Bot + Users |
Requirement | Use when need to send message as a User | Use when need to send message as a Bot |
Forbidden scopes | Does not accept Bot scopes; providing them leads to authentication failure. | Does not accept User scopes; providing them leads to authentication failure. |
