Action items hide inside long email threads and quietly slip through the cracks. Forward a message or add a label and this agent reads the thread, pulls out the real task, and files it in Notion with an owner and a due date.
sonnet3 daysGmailClaudeNotion APIGoogle Workspace
Claude
84ROI
74Scale
$2.5k86Saved
ROI for
README.md
Why this subagent
Action items hide inside long email threads and quietly slip through the cracks. Forward a message or add a label and this agent reads the thread, pulls out the real task, and files it in Notion with an owner and a due date.
Each task links back to the original email, so context is one click away. It tracks thread ids to avoid creating duplicate tasks, so the same request never lands in your board twice.
How it runs
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
Extract the request, owner, and any deadline mentioned in the thread.
pending
Create a Notion task with title, due date, priority, and a link back to the email.
pending
Reply or comment to confirm the task was filed and store the thread id to prevent duplicates.
pending
Sample output
json
// Sample output
// (generated when the pipeline finishes)
From this email thread, return JSON with task title, owner, due date, priority, and a one-line summary.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.