Within this space, you should see your Storytell appReminder: 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!
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.
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.
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)
.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.
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)
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
@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
@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.