School Inbox Lite
Kids have no email, so the parent inbox is the family's only source of truth for what school needs. This reads school-origin mail (Google Classroom guardian summaries, PowerSchool and SwiftK12 attendance, ParentSquare, ClassDojo) and turns each message into a typed event: which child, what it is, the deadline, the action. Every event gets exactly one label and every deadline gets an owner, so nothing slips past pickup.

Triage school email into typed events with owners. Use when school email needs processing, the parent asks what's due or what they missed, or a deadline, permission slip, or schedule change needs extracting. A Connie Ector recipe for parent agents.
How it works
- 1Sweep the inboxSearch the window for school-origin senders: Classroom guardian summaries, PowerSchool/SwiftK12 attendance, ParentSquare digests, ClassDojo, plus any sender the parent confirmed before.
- 2Type every emailOne event per email: child, category, deadline, action. Login-walled links are never followed; they become authenticate-to-view items.
- 3Label and actExactly one label per event. Ready-for-agent items (calendar adds, reminders, known-answer RSVPs) are done immediately; ready-for-kid items become Sprout tasks only after the parent confirms.
- 4Report with ownersOne line per event: child, what, deadline, label, owner. Every deadline gets an owner; nothing is silently dropped.
Instructions
Email is the school's API. Kids have no email, so the parent inbox is the family's only event source.For the window in question (default: the last {{input.window_days}} days, or 7 if not given):1. Search the parent's inbox for school-origin senders, plus any sender the parent confirmed previously. Fingerprints: no-reply@classroom.google.com (subject "Daily summary for ..." or "Weekly summary for ...", sections for missing work and upcoming work; summaries list work, they do NOT confirm submission, so follow-ups stay waiting-on-school). @swiftk12.com, @schoolmessenger.com, or district domains (attendance notices, terse and same-day; grade digests periodic). donotreply@parentsquare.com (three lanes: instant posts, daily digest, urgent; the digest repeats instant posts, dedupe by post title). @classdojo.com (teaser-only behavior points and teacher messages; the value is that something exists, and which kid).2. Type each email into one event: child, category, deadline, action. Categories: assignment, grade, absence, permission_slip, schedule_change, behavior, billing, general. Never follow login-walled links: type the event authenticate_to_view and move on.3. Label each event exactly once: needs-parent (judgment required), waiting-on-school (ball in their court), ready-for-agent (fully specified, no judgment left: calendar add, reminder task, RSVP with a known answer; do these now), ready-for-kid (becomes a Sprout task via task.create only after the parent confirms it), wontfix (noise, say why once).4. Report one line per event: child, what, deadline, label, owner.Completion: every school-origin email in the window has exactly one label, and every extracted deadline has an owner: parent, agent, or kid-task. An email that resists typing becomes a needs-parent event carrying its subject line. Nothing is silently dropped.
Inputs
- Window (days)
window_daysHow many days of school email to triage. Defaults to 7 or since the last run.