In this episode, Jason connects a daily email triage to a Notion database and logs the morning run automatically. He starts with one row per email, decides that's overkill, and iterates the layout live to one row per day with a summary. The bigger idea: stop letting work disappear inside chat threads. By storing triage results in Notion, you build a knowledge base that a future daily briefing can pull from instead of re-checking your inbox. He closes by updating the scheduled task and skill so every morning run writes one summary row to Notion on its own, with no chatting required. Tools shown: Claude Cowork, Notion, Gmail connector, scheduled tasks.
Back to library
9:50 · Jun 14, 2026
Scheduling Claude's Email Triage Task to Notion
Take a working email triage and wire it into Notion, then iterate the database from one row per email to a clean daily summary, and update the scheduled task so it writes there every morning.
Transcript preview
After this run finishes, I come over to Claude. There are a few ways to do this, but I'm just going to grab the last run and say: we now have a daily email triage database in Notion. Connect to this DB and store this information there. (Yes, I said please. You can do that.) I can even type the instructions sloppy and misspelled, and it still works.Now it learns about the connector and goes to find the tool. You can see it finding them. One of the connectors it's using is the Gmail connector, and we can see it just added the Notion connector. It's going to take what it did on the 5 a.m. run and…
More on Claude
KEEP GOING
intermediate
6:47
Free intermediate
ClaudeNotionEmail
Claude + Notion: Email Triage Review and Next Steps
intermediate
6:26
Pro intermediate
ClaudeAutomationNotion
Stop Building Notion Pages or Databases by Hand
Go Pro to watch →
beginner
9:28
Pro beginner
ClaudeClaude SkillsOperations
Your First Claude Skill: Email Triage in One Prompt
Go Pro to watch →