While managing your Slack app settings, you'll find a snippet of HTML customized for your application under
Manage Distribution. It's a simple
META tag declaring your Slack app's ID, which typically begins with
A. If you already know the ID, you can build one of these tags yourself.
The snippet looks something like this:
<meta name="slack-app-id" content="YOUR_APP_ID_HERE">
Place this brief piece of HTML in your website template's
HEAD section, beside other metadata rubble you've accumulated, like so:
<html lang="en"> <head> <meta charset="utf-8"> <meta name="slack-app-id" content="YOUR_APP_ID_HERE"> <title>Beforebot highlights bots before it</title> </head> </html>
With this HTML in place, Slack is ready to suggest your app to new users on teams it isn't yet installed on.
Let's take a hypothetical example.
@beforebot is a Slack app in the directory that has placed its app ID meta tag in the template of all pages on
On a team where
@beforebot is not installed,
@ada posts a message talking about the link
Within moments of posting, Slack crawls the URL and extracts the app ID, correlating it to the
@beforebot app. Slackbot then posts an ephemeral message only
@ada can see:
This message contains the app's icon and short description, along with a link back to the app directory. It also contains three decisive links:
@adato the app directory
@adaagain when posting links to
@adato install again
As you can see, app suggestions are a fantastic way for users and teams already engaged with your product or service to discover your Slack app.
Once installed, your app can attach custom unfurling behavior to relevant links shared in messages, among all the other nifty things bots and apps can do.