How to install Storytell in my Slack Workspace?

Shortlink: http://go.Storytell.ai/Docs

Install Storytell in Your Slack Workspace

The easiest way to start using Storytell is to join our Slack Playground. If you want a custom install in your own Slack workspace, here’s how!

You’ll need a Slack Admin to configure Storytell. If that’s not you, share this with the appropriate person in your company.

⏰ This process will take you around 10-15 minutes

Create a new “Bot” in your Slack workspace

Click here to start and then click Create app

2. Select your workspace in the popup window

3. ClickEdit Configuration

❗Warning: Do not click the green Create button. (Don’t let it trick you!)

4a. You’ll need to copy this configuration below

_metadata:
  major_version: 1
  minor_version: 1
display_information:
  name: Storytell (Storytell Official App)
  description: Distill Signal from Noise
  background_color: "#11359e"
features:
  app_home:
    home_tab_enabled: false
    messages_tab_enabled: true
    messages_tab_read_only_enabled: true
  bot_user:
    display_name: Storytell
    always_online: true
oauth_config:
  scopes:
    bot:
      - app_mentions:read
      - channels:history
      - chat:write
      - files:read
      - files:write
      - groups:history
      - groups:read
      - im:history
      - im:read
      - mpim:history
      - mpim:read
      - users:read
      - channels:manage
      - groups:write
      - im:write
      - mpim:write
      - chat:write.public
      - chat:write.customize
      - channels:read
settings:
  event_subscriptions:
    bot_events:
      - app_mention
      - message.channels
      - message.groups
      - message.im
      - message.mpim
  interactivity:
    is_enabled: true
  org_deploy_enabled: false
  socket_mode_enabled: true

4b. You’ll copy the text above by hovering over this button as per the instructions below:

5. Paste it in to your screen where it says Enter app manifest belowin the YAML configuration (not JSON). Then hit Next (green button)

6. Now hit the green Create button to save the configuration

7. Go to App Home

8. Scroll down in App Homeand hit “edit” next to App Display Name

9. Name the app Storytell [your workspace name] (can be with dashes or without)

10. Download this Storytell app icon if this is your first install (if you’ve already installed Storytell in another workspace, you may still have the icon)

11. Now it’s time to add the Storytell icon — you might find it by scrolling down OR you may have to go to Basic Information to alter the Display Information

Within Basic Info, scroll down to Display Information— this is where you’ll update the app icon by uploading the Storytell icon

You can save changes once you’re done. If the save changesbutton doesn’t appear to do much, it auto-saved, so you’re all good 👍

12. Scroll back up within Basic Information. Then select **Install to Workspace**

13. You will see this interface. Select allow

14. Get a Slack App authorization token

Go to https://api.slack.com/apps to find your bot.
Within this space, you should see your Storytell app Reminder: the name of your app will be Storytell-your-worksopace-name
The current status for this app should be not distributed
Select generate token

5. Select your app from the list

6. Now we need to get your app level token. To do that, go back to the URL where you’ve been installing the bot into your workspace. Here’s what that journey might look like.

7. Scroll down to App-Level Tokens and click Generate token and scopes

8. Name the token Storytell

9. Click Add Scope

10. Add scopes by copying and pasting this text: connections:write and authorizations:read (It’s possible that these scopes could pop up for you in the dropdown menu as options to select)

15. Click the Generate button ☝️as seen above

16. Another popup with a token will appear. Copy it and save the token (you’ll be sending it to us in a bit — unless you have multiple copy / paste, you’ll need to paste it on a sticky note, etc, temporarily). Because there’s one more token you’ll need to grab!

17. Click done on the token popup

18. Go to 0Auth & Permissions

19. Copy the OAuth token

20. Send all the tokens to the Storytell team athello@storytell.ai

- This includes
  - App-Level token
  - 0Auth Token

The Storytell Founders and our Customer Experience team need to be in one private channel in your workspace to QA future Storytell deployments in your workspace. You’ll need to do this so we can provision a server for you.
1. Create a private channel called #storytell-testing-[your workspace name] whether your workspace is free or paid
  1. Free / regular Slack workspace
    Invite us to your workspace (yes, we’ll have access to the entire space, but we’ll just stay in our lane in a testing channel)
    Create a private channel within your workspace and add us to it
    jingconan@storytell.ai, drodio@storytell.ai, erika@storytell.ai, patrick@storytell.ai

Premium Slack workspace
1. Invite as single channel guests in a private channel
  1. jingconan@storytell.ai, drodio@storytell.ai, erika@storytell.ai, patrick@storytell.ai

21. We will provision a server for you within 24 hours

How will we notify you? Wherever we’re already communicating with you.
- If we’re already in communication over Slack, it will happen there. If we have a private channel with you, this will be the place.
- If we’re in communication over email, we’ll let you know via email.

22. Once we let you know the Storytell app is provisioned, you can add it to any channel in your Slack workspace. To add it to a channel:

Just @ Mention @Storytell in the channel like this. You’ll see a button that says invite them — or you may see a popup with a green button that says Add to Channel

🎉 You did it! Storytell will now run automatically in your Slack workspace in any channel where you have invited Storytell to run, as shown above ☝️

23. Let your workspace know that Storytell is running! Sample message — feel free to copy and paste.

Hi everyone!

I’ve just installed the Storytell Slackbot in our workspace, which will automatically recognize the following types of content and give us the ability to turn it into summaries, exec summaries, blog posts, etc using AI.

For now, go to [name of channel where Storytell is running] to drop in one of these kinds of files:

YouTube video URL
Zoom Recording URL (and passcode)
CloudApp URL
MP4 upload
.txt or .zip File attachment
Any long block of text -- or long Slack message
embedded Slack audio or video recording

Please rate the reports and give feedback as they founders are iterating based on your experience. And if you want to add Storytell to another channel, all you have to do is at mention and invite it.

Sample content you could share:

YouTube https://youtu.be/XUa7I8TXqZo

“Zoom to Slack” Setup:

You can use Zapier to automatically push your Zoom recordings into Slack, where Storytell will automagically run Storytell reports on them.

Configure Zoom to share your recordings in a specific way:

Ideally, the Zoom Admin of your company can toggle these settings for all users so each user doesn’t have to do it individually:

Have the admin go to Zoom Admin >> Account >> Settings >> Recording
Change this Cloud recording download setting to “on”:

Change this Require users to authenticate before viewing cloud recordings setting to “off”

Your videos will still be secure because people won’t be able to access them unless they know the passcode. Our crawler is in a “logged out” state so cannot access the videos otherwise.

If you can’t have the admin globally change these settings, you can do it in your zoom account, like this:

Go to Zoom Personal >> Settings >> Recording
Update the same two settings above for your account.

You can also edit settings to share your past meeting recordings on a per-video basis.

Make two adjustments in the sharing options to make it work for Storytell:

Go to Zoom Personal >> Recordings
Configure Zoom to share your past recordings “publicly” (but still with a passcode), like this:
1. Change Only authenticated users to Publicly .
2. Enable the Views can download option, which would allow our crawler to download the data.

If you click the Share button next to each video you will be able to see the popup.

Your videos will still be secure because people won’t be able to access them unless they know the passcode. Our crawler is in a “logged out” state so cannot access the videos otherwise.

Set Zapier up to push your recordings into Slack:

Zapier is a platform that connects one service to another.

👉 Make a copy of this Zap to connect your Zoom account to your Storytell Slack channel

That’s it! Storytell will run automatically every time you share a Zoom recording, like this:

Using Storytell: Summarize Videos & Text with Storytell Slack Bot

Storytell will run automatically any time the following URLS are dropped into a Slack channel that includes Storytell:

Zoom cloud recording URLs (include the passcode if it has one)
YouTube URLs
CloudApp URLs

Storytell will also run automatically in any Slack channel when:

There’s a long Slack message (over 500 characters)
There’s an attachment to a message (like a .txt file)

You can also manually use @Storytell in any Slack channel you’ve invited the bot into. This is helpful when you want to summarize a long Slack thread or upload a .txt transcript from a service that Storytell doesn’t yet support automatically. Here’s how:

Summarize any Slack Message, Thread or Text File

To summarize Slack messages or threads: Run one of the commands below on an existing Slack message or thread.
To summarize text files: Create a new Slack message and upload a .txt file with your raw source content (typically a transcript). It can be of any length, and run one of the commands below to transform the text:

@Storytell - This is the default action and creates a summary of the source text @Storytell tldr - Create a shorter summary of the source text than the base command

Examples: Slack Message

User types “Storytell” on a long Slack thread to get a summary returned:

Double click to enlarge

Additional (Advanced User) Modifier Commands:

-max_tokens [number] - Specify the maximum size of the output that’s returned by StoryTell -temperature [value] - Specify a value between 0.0 to 1.0. The higher the value, the more creative & random StoryTell will become in its responses. We generally recommend temperature values between 0.49 to 0.7.

-model [model name]

Improve StoryTell’s Accuracy

Available Commands:

@Storytell bug [detail on the problem] - If you think there’s a bug, file a ticket with this command @Storytell feature [detail on feature request] - If you’d like Storytell to work in a different way, file a feature request with this command @Storytell feedback [detail on your feedback] - If you have feedback that’s not exactly a bug or a feature request, use this. For example, maybe you’re confused about how something works.

Examples: Improve Accuracy

Running “@Storytell rate [score] [explanation]”

Running the “@Storytell feature [detail]” command to request a new feature

Running the “@Storytell bug [detail]” command to submit a bug ticket:

Double click to enlarge

Commands for Advanced Users

Available Commands:

@Storytell run [more detailed input command] - You can optionally add a more detailed input command, which you do by adding a code block. See the example below.