taskflow-inbox-triage

Automating inbox triage uses a single-owner flow to classify messages, route business items to Slack with a waiting state, and hold other items for end-of-day summaries. It persists routing state in stateJson and resumes when external replies complete.

Routing state persists by saving context in stateJson and waitJson during detached classification tasks. The flow resumes automatically when external input completes, coordinating multi-step triage processes until all waiting items resolve and the batch finishes.

Routing personal inbox items separately triggers immediate owner notifications, while business messages route to Slack with a waiting state. Everything else queues for end-of-day summaries, ensuring unified triage across both personal and shared inbox items.

Consolidating unresolved inbox items for end-of-day summaries involves holding non-business and non-personal messages in a queued state. The single-owner flow batches these remaining items, finishing once all routing and waitJson resolutions complete.

Inbox triage works for personal assistants by applying a deterministic single-owner flow to shared inboxes. It classifies messages, routes them to Slack or owners, and coordinates multi-step waiting states, suiting assistants managing mixed business and personal items.

A batch flow holds items instead of routing immediately when they do not match business or personal classification criteria. These unmatched items remain in a persisted waiting state for end-of-day summary consolidation rather than triggering immediate notifications.