Using Collections in Workflows

Collections are not just for organization. They actively shape how you interact with Storytell. Once you have created a view, you can use it in multiple places.

Written By Patrick Intervalo

Last updated 2 months ago

After creating a Collection, you can put it to work in different parts of Storytell. The examples below show how views shape prompts, the Knowledge Pane, and project organization, with more automation features on the way.

In Prompts

Mention a Collection by name to set it as your scope. This tells Storytell to only use the Assets inside that view when answering

  • Example: @Customers summarize key complaints across interviews.

  • Instead of searching through all Knowledge, Storytell only pulls from the Assets inside the “Customers” Collection.

In the Knowledge Pane

Each Collection lets you see both:

  • Assets: The files or uploads inside the view.

  • Concepts: The ideas and insights extracted only from that view.

This dual perspective helps reduce noise. Instead of scrolling through Concepts from your entire Knowledge base, you can narrow down to just the Concepts related to a project. For example, flipping from “All Knowledge” to “Customer Research” will show only customer-related Concepts.

For Projects

Collections keep projects contained. Instead of mixing every file in your workspace, you can create project-specific scopes.

  • Example: A “Q4 Marketing Plan” view that includes only campaign Assets and market research.

  • This makes it easier to share context with teammates and avoid irrelevant data.

Future Automations (Coming Soon)

Dynamic Collections will eventually support automated triggers. You will be able to tell Storytell:

  • “When a new Asset is labeled Invoices, rerun my ‘summarize financials’ prompt.”

  • “When customer feedback files are added, refresh the customer insights summary.”

This turns Collections into live, self-updating resources that save time and keep insights current.