Slack 2.0 Integration with Simpplr

Table of Contents

Overview & key benefits

Security permissions and scopes

App manager settings 

User connection 

Site settings

New and updated features

Migration from legacy Slack

Known issues and FAQ

Slack Integration 2.0 Overview

This Slack integration with Simpplr is all new, built-from-scratch to utilize the latest Slack APIs, which give us more functionality, including:

  • Renaming of the bot name and icon
  • New unfurl image and text cards
  • The ability to sync threaded responses
  • Click2Chat
  • Emoji support
  • @mentions
  • #channel names
  • Engaging with content in Slack
  • Improvements to sharing and promoting content

If you've used the Slack integration before and want to upgrade to 2.0, you'll need to migrate from the previous Slack integration to this new integration. This will require App managers to head to Manage > Application > Integrations and updating their org's Slack connection with Simpplr.

Key benefits of using Slack with Simpplr

  • Better organizational alignment

    • Keep employees on the same page, regardless of their preferred communication channel

  • Unify and streamline communications

    • Centralize communications to maintain up-to-date information on both platforms, reducing the need to switch between multiple platforms

  • Improve collaboration and engagement

    • Integrate with Slack to offer employees a familiar platform, encouraging greater engagement in intranet discussions and events

Security permissions and scopes

When first integrating Simpplr with Slack, you might encounter various permission requests. These permissions determine what Simpplr can do within your Slack workspace. Here's a breakdown of the permission requests you might see and what they mean:
Slack 2.0 permisisons.png

On behalf of users, Simpplr can:

  1. View information about a user's identity: This permission allows Simpplr to access basic information about users' identities in your Slack workspace. It includes details like display names, profile pictures, and possibly email addresses. This information helps Simpplr provide a more personalized and user-centric experience.

  2. View messages and other content in a user's public channels: Simpplr is requesting the ability to access messages and content posted in public channels where the user is a member. This permission enables Simpplr to provide relevant services or interactions based on the content within those channels.

  3. View basic information about public channels in a workspace: Simpplr aims to access basic details about public channels in your Slack workspace. This includes channel names and member lists. This information could be used for providing context or facilitating interactions.

  4. View basic information about a user's private channels: Similar to public channels, Simpplr wants to access basic information about private channels where the user is a member. This ensures that Simpplr can operate effectively within those private spaces.

  5. View people in a workspace: This permission allows Simpplr to access a list of users who are members of your Slack workspace. It helps Simpplr provide insights, interactions, or features that involve workspace members.

  6. Send messages on a user's behalf: Simpplr is requesting permission to send messages in Slack as if they were sent by the user. This could be for personalized interactions, announcements, or other relevant communications.

  7. View URLs from and Simpplr aims to access and view URLs from the specified domains posted in messages. This might involve displaying previews or processing content from these URLs.

On behalf of the app, Simpplr can:

  1. Send messages as @simpplr3: This permission allows Simpplr to send messages in Slack using the username @simpplr3. These messages might contain information, updates, or interactions from Simpplr.

  2. Send messages to channels @simpplr3 Isn't a Member of: Simpplr is requesting the ability to send messages to Slack channels where @simpplr3 isn't a member. This could be for sharing relevant information or participating in discussions.

  3. Send messages as @simpplr3 with a customized username and avatar: Simpplr aims to send messages using the username @simpplr3 along with a customized profile picture. This allows Simpplr to maintain a consistent brand presence and recognition.

  4. View [company domain] URLs in messages: Simpplr is requesting access to view URLs from your specified company domain that are posted in messages. This might involve displaying previews or processing content from these URLs.

  5. Show previews of [company domain] URLs in messages: This permission enables Simpplr to display previews of URLs from your company domain when they're posted in messages. It allows users to see a snippet of the content before clicking on the link.

Bot token scopes 

  • chat:write

    Used when the message is posted to Slack via Bot in Simpplr. Simpplr application calls API chat.postMessage to post the messages

  • chat:write.customize

    Used when customizing the app icon and app name while posting the feed or content to Slack channels

  • chat:write.public

    Send messages to public channels on Slack where the @Simpplr application is not a member of

  • chat:write.public

    Simpplr has a feature of message unfurling, where if we copy and paste the link of a feed or content in Simpplr to Slack channel, it gets unfurled. This scope is used to fetch the events for unfurling for specific domains like,,, and

  • links:write

    Simpplr has a feature of message unfurling, where if we copy and paste the link of a feed or content in Simpplr to a Slack channel, it gets unfurled. This scope is used to show the preview of urls pasted in the Slack channel for unfurling the links for specific domains like,,, and

User token scopes 

  • channels:history

    Receive the message posted in the Slack channel as event. This is used in the threaded response feature, where we get messages from 'Slack To Simpplr'. This scope is used to fetch the message event for the message added in Slack

  • channels:read

    Get a list of channels of users in the Manage > Site section. Users can select the channel of Slack to which feed and content should be posted

  • chat:write

    Post a message to a channel on user's behalf while posting or promoting a content or feed. This is used while using the API

  • groups:read

    Get a list of channels of users in the Manage > Site section. Users can select the private channel of Slack to which feed and content should be posted

  • links:read

    Simpplr has a feature of message unfurling, where if users copy and paste the link of a feed or content in Simpplr to Slack channel, it gets unfurled. This scope is used to fetch the events for unfurling for specific domains like,,, and

  • users:read

    Retrieve user's name and their profile ID for our Click2Chat functionality, which is visible on a user's profile page


App manager settings 

Connection will remain the same for App managers.

  1. Head to Manage > Application > Integrations > Messaging. If you've connected before, you'll be asked if you want to upgrade to Slack 2.0. Doing so will redirect you to Slack, where you'll be asked to authorize the permissions from Simpplr.
    Slack 2.0 auth app manager.png


App managers will notice an additional option after enabling Slack for their organization and logging in. Our Slack integration now allows organizations to customize the Slack bot image and name. The recommended image size is 512x512px. Images larger than this will not be accepted. 
Slacik new 1.png

This custom name and icon will be displayed when auto-posting content such as site feed activity to Slack, as well as when replies are syncing between Simpplr and Slack.
Slack new look 1.png


If you disable the connection at the app level, it stops the Simpplr bot from auto-posting at the site level.

User connection 

All users on the new Slack integration (including the App manager after connecting at the app level) will be required to connect their Simpplr profile to Slack again. This can be done from their user menu > Profile & settings > Edit profile & settings > External apps. Similar to App managers, users will be redirected to Slack to authorize the requested permissions from Simpplr to Slack.
Slack 2.0 user auth.png

Users who have not connected their profile to Slack in the past will be prompted when they paste a Simpplr link into Slack with three options. These options will only appear when the Simpplr Slack App is installed (i.e., the app is enabled at the application level):

  • Clicking Connect will open a window for the user to give us their Slack permissions to finish connecting their account for the Simpplr/Slack integration.

  • Clicking Connect later will dismiss the connection prompt until a new Simpplr link is pasted in Slack.

  • Clicking Don't ask again will stop the prompt from appearing and require the user to connect Slack via their profile page.
    Slack new 4.png

Site settings (new unfurl preview settings, warnings, nested settings, About section, type and search for channel)

We've made improvements to selecting site feed activities with nested options for posts, comments and replies, or just posts and comments.
Slack new 5.png

With the Slack 2.0 integration, we've made it easier for Site managers to connect a site feed to Slack. Just type and search to find all channels where you have posting privileges to select from.
Slack new what to post.png

Sites that link to Slack will show the Slack channel in the site about page with a link to that Slack channel.

Public sites

Site managers of public sites can control if content is unfurled (a preview of the content is shown) when shared with Slack. By default, the unfurl option is enabled for public sites. To enable or disable this setting, head to Manage site > Setup and scroll down until you see the option. 
Slack bnew unfurl.png

When a user shares or promotes content from a site with unfurl disabled, they will see this warning message:
Slack new unfurl 2.png

Private and unlisted sites

Site managers of private sites can control if content is unfurled when shared with Slack. By default, the unfurl option is disabled for private and unlisted sites. Again, this option can be enabled by going to Manage site > Setup
Slack new private sites.png

When a user shares or promotes content from a private site with unfurl enabled, they will see this warning message:
Slack new private sites 2.png

If the site is private or unlisted and unfurling is disabled, sharing to Slack will be disabled. Additionally, all sharing to Slack is disabled for unlisted sites.
Slack 2.0 private site warning.png

New and updated features


When you add your Slack profile to Simpplr, a new icon will appear in your profile and areas throughout the intranet so other users can start a direct message (DM) with you:

On your user profile:
Slack new user profile.png

In the people list:
Slack new people menu.png

On the site member list:
Slack new site member.png

Preview cards

This is likely the biggest difference you'll notice from the previous version of the integration. We've removed the majority of visible links when sharing, promoting, and site feed activities. Now, you'll see hyperlinks and actual content in place of links.

Promoting and sharing content
Slack new sharing content.png

Site feed content
Slack new site feed content.png

Site feed posts
Slack new site feed posts.png

Pasting in a Simpplr url
Slack new pasting in a Simpplr URL.png

Engaging with content

When a content link is pasted in Slack, content will unfurl and display three quick action buttons; like, favorite and comment. Users can like and favorite Simpplr content from within Slack, and these actions will reflect in Simpplr. If a user clicks Comment, they'll be taken to the content, where they can comment. A comment directly on the content cannot be made through Slack, which is why users get directed to the content feed within their intranet to leave a comment. However, replies to that initial comment can be made directly in Slack, and will sync back to the Simpplr content. Think of replies and comments as two separate actions here. Replies to comments can be synced from Slack to Simpplr, but comments must be made in Simpplr.
Slack new engage with content.png


Sharing content to Slack channels just got much easier by way of typing out Slack channel names and not having to copy Slack channel URLs anymore. Content shared will be displayed by the user sharing (not by Slack app) to further enhance engagement in Slack.
New Slack sharing.png


You can promote your content to Slack by typing in the Slack channel name(s) when prompted to promote. You'll no longer need to copy multiple Slack channel URLs. You can promote your page, event or album to up to five Slack channels at once. Content promoted will be displayed by the user promoting (not by Slack app) to further enhance engagement in Slack.
Slack new promote content.png

Content comments, site feed posts and replies will sync with Slack, but content comments and replies will appear the same way feed post interactions do.

Threaded responses (mentions, emojis, etc)

Site feed posts and replies can sync between a site and a selected Slack channel if enabled in Manage site > External apps.
Slack new site settings.png

The content will look like this:
Slack new Simpplr convo.png

Syncing site feed posts and replies support the following:

  • Standard emojis will display in Simpplr and Slack

    • Custom uploaded icons will display as :text:

  • #Topics and @Product mentions in Simpplr will show up as a hyperlink in Slack back to Simpplr

  • Slack #channel names will show up as hyperlinks in Simpplr

  • Slack @people mentions will show up as @mentions in Simpplr

    • The user mentioned must have their Slack profile connected to Simpplr for this to work

Migration from legacy Slack integration

Since we created a new Slack app with their latest API's, App managers will need to migrate to our new Slack integration. We made the upgrade process straightforward and easy. Upon clicking Upgrade in Manage > Application > Integrations > Messaging, they will disable the old Slack app integration in the background, remove the old Slack bot, install our newest Slack integration app, and land on the Slack authorization page. Simpplr will also send a notification to Site owners who set up their site feeds to Slack in the past, asking them to reconnect. End users will also need to reconnect their profiles if they had before with the old integration. This results in a migration process that only requires two clicks (one click on Simpplr, one click on the Slack auth page).

App managers will see this in Manage > Application > Integrations > Messaging.
Slack new App manager auth.png

Clicking Find out more will show:
Slack 2.0 notice .png

This message will let you know that upon upgrading, all End users and sites previously connected to Slack will need to reconnect. You'll be given the option to download a CSV file of all previously connected sites. This CSV will always be available in the Manage > Application menu.
Slack 2.0 previously connected sites.png


After the upgrade completes, App managers can customize the name and icon.
Slack new App manage customize .png

Out of scope and known issues

  • Sites and user profiles are currently not supported for unfurling when sharing/promoting or copying/pasting links

  • Site feed posts syncing to Slack support basic formatting:

    • Bold, italic, strikethrough, simple unordered lists, simple ordered lists

  • Interactive features are not yet supported in direct messages

  • Sharing/promoting content will not show as a new message for the user sharing/prompting in the destination Slack channel (others will see new message)

  • Slack private channel threaded replies will not sync back to Simpplr

  • Custom App name and icon

    • Unfurling (copy paste link) will still show the Simpplr name
      Slack new known issues 1.png

    • Collapsed threaded replies in both feed posts and content posts will show the Simpplr logo instead of your company's custom image.
      Slack 2.0 threaded replies image.png

Known issues

  • When promoting content from a private, non unfurling-enabled site, the option to share to Slack still appears
  • Feed posts, Recognition posts and Blogs do not unfurl
  • Page sharing is not fully unfurling
  • When promoting content to Slack, there is no longer a Like button within the new Slack app. End users will see a 'view page' instead.
  • Custom images uploaded are blurring 
  • Comments on site-level are appearing as site feed posts
  • Gaps in page threading
  • Not able to crop customized images
  • Nudges to connect using Slack image is not the custom Simpplr bot image
  • Removing tokens when deciding a site shouldn't unfurl
  • You currently cannot upload a custom image outside the recommended aspect ratio (512x512 px)


Q: Do links unfurl that contain domains that Salesforce would typically redirect, such as pre-enhanced domain? In other words, would <org name> unfurl?

A: Only URLs ending in the following domains will get unfurled in both Slack 1.0 and Slack 2.0:



Q: Do Salesforce Hyperforce upgrades change the product's URLs?

A: No. Hyperforce migration in itself does not change the URL. If you had not enabled enhanced domains before the Hyperforce migration, and the URLs had an instance name in them (na103), then the URLs are changed as migration puts them on a new instance.

Q: Does Simpplr use services or an external service outside of Salesforce to make posts from Simpplr to Slack?

A: No. Only Apex and our own micro-services are used with Slack. No external or third party service is used.

Q: If you switch a site from private to public or vice versa, does the default setting for content unfurling change?

A: Yes, unfurling configurations will revert to the default settings. On Public sites, unfurling is enabled by default. With Private sites, it is disabled by default.

Q: How do custom Slack app name and images work? How long does it take for the app on the Slack Side to update? Does it rely on apex jobs or an external service?

A: No apex jobs or an external services are involved. It's a synchronous process, and any update to your custom Slack app name and image should be available as soon as the API is complete and success response is received.

Q: What happens if we use custom-uploaded emojis in a Slack thread with a site connection? How will that appear in Simpplr?

A: Default Slack emojis are supported, and will appear as expected, custom emojis that you upload within posts/replies are not supported. Emoji code will be displayed instead (e.g.,  ":<emoji-name>:")

Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request



Please sign in to leave a comment.

Articles in this section