taskflow-inbox-triage

Inbox triage automation classifies messages by intent and routes them immediately: business items go to Slack threads, personal items trigger owner notifications, and remaining items are held for an end-of-day summary.

A batched workflow uses a wait state to block processing until external replies arrive, then resumes automatically to complete routing. This ensures all items are classified and routed without manual intervention.

Yes, routing state is persisted in stateJson to track business, personal, and end-of-day routes independently. The workflow transitions to a waiting state only when external input is required, then resumes to finish routing.

Separating business and personal notifications requires classifying each inbox item by intent first. Business items route to Slack threads, personal items trigger immediate owner notifications, and everything else is deferred to an end-of-day summary.

No external dependencies or components are required to run inbox triage. The workflow operates independently, using internal state management to classify, route, and persist decisions across business, personal, and summary routes.

A single-owner batch workflow is not suitable when multiple owners need to triage simultaneously or when messages require real-time routing without batch classification. It is designed for a batched flow with one owner handling all routing decisions.