How to Build a Daily Workflow in Tana With AI Supertag Autofill
A Tana daily workflow is a set of supertags plus search views that assemble themselves each morning: a #Day node that pulls open #Task items, meeting notes captured during the day, and AI autofill filling owners and due dates from raw text. You build it once and it runs on every new day node.
The reason to invest an hour here is that Tana does not care where a node lives. A query can surface every task in the workspace, so your “today” view is generated, not maintained.
What is the core pattern?
Templates plus queries. A supertag can define a template — child nodes that appear automatically when you apply it. A search node with a query filters by tag and field. Together they make a day page that builds itself.
You need three supertags to start: #Task (Status, Due, Owner), #Meeting (Attendees, Project, Actions), and #Day (Date, Focus).
How do you set up the Day template?
- Create a #Day supertag with a Date field defaulting to today.
- In its template, add a search node filtered to #Task where Status is not Done, sorted by Due.
- Add a second search node for #Meeting where Date is today.
- Add a plain Notes section for free typing.
- Each morning, create a node, type #Day, and the three sections appear populated.
The search nodes are the payoff. Because they are live, a task you add at noon shows up in the morning view the moment it exists — no dragging into a board.
Where does AI autofill fit?
Autofill shines on capture, not planning. When you jot “call Marcus about the Q4 budget, follow up Thursday,” trigger AI on the #Task supertag and it extracts the action, sets a due date, and guesses the owner.
You can also run an AI command over a #Meeting node to summarize discussion into action bullets. Treat its output as a draft. The model occasionally assigns an action to the wrong person when two names sit in one sentence, so scan the fields before trusting them.
What queries keep the workflow from rotting?
| View | Query | Purpose |
|---|---|---|
| Today | #Task, Due ≤ today, Status ≠ Done | What is actually due |
| Waiting | #Task, Status = Waiting | Blocked items to chase |
| Unsorted | #Task with empty Due | Catch untriaged captures |
| Log | #Day sorted by Date desc | Review past days |
The Unsorted view matters most. Without it, autofilled tasks that miss a date quietly vanish from your today view and pile up untracked.
How many supertags is too many?
Past about 8 to 10 active supertags, most people stop maintaining them and the workspace becomes noise. Start with Task, Meeting, and Day. Add Project only when you have more than one running at once.
Each new supertag is a schema you must keep consistent. If you are the only maintainer and you do not enjoy data design, three is plenty.
Who gets value from this build?
Solo operators juggling calls and deliverables who already think in outlines. If you plan once a week and execute, a simple to-do app is lighter. This rewards daily use and someone willing to tune queries rather than accept defaults.
Quick Summary
- A Tana daily workflow is built from #Day, #Task, and #Meeting supertags plus live search views.
- Search nodes generate a today view automatically — no manual moving of tasks.
- AI autofill is best for capturing raw text into structured fields, not for planning.
- Keep active supertags under about 10, or the workspace turns into untended noise.
