# Collections


Collections are folders for notebooks. Use them to create lanes for projects, workflows, and playlists.

:::tip Video walkthrough
[Watch on YouTube](https://www.youtube.com/watch?v=0j7vD5gCX2c)
:::

## What Collections Are For

- **Project grouping** - Keep related notebooks together
- **Workflow lanes** - Inbox → Active → Archive
- **Audio lanes** - Use a collection as a podcast queue via [The Pipeline](#)
- **Standardization** - Trigger templates or artifacts when notebooks enter a collection

## Common Collection Patterns

- **Inbox / Active / Archive** - A simple lifecycle for everything you save
- **Topics** - Health, Finance, Career, Learning
- **Clients** - One collection per client
- **Media Queues** - Daily Read, Commute Queue, Workout Queue

## How Collections Work With Automation Rules

- **Auto-file with tags** - [Smart Sort](#) can move notebooks into a collection when you apply a tag
- **Auto-create structure** - [Template Engine](#) can create notes when a notebook enters a collection
- **Auto-generate audio** - [The Generator](#) can generate audio when a notebook is added to a collection
- **Auto-queue audio** - [The Pipeline](#) can send notebooks in a collection to a podcast feed

## Example: Collection as a Listening Queue

1. Create a collection: _Daily Read_
1. Enable [The Generator](#): when notebook enters _Daily Read_ → generate audio
1. Enable [The Pipeline](#): _Daily Read_ → Podcast _Morning Commute_
1. Enable [The Cleaner](#): finished episode → remove it

## Pro Tips

- **Use collections as triggers** - they’re easier to reason about than many overlapping tags
- **Keep names action-oriented** - _To Read_, _To Write_, _Deliver This Week_
- **Don’t over-nest** - a few high-signal collections beat dozens of micro-folders