clawflow-inbox-triage

Inbox triage routes messages by classifying intent into business, personal, or other categories. Business threads post to Slack and await replies, personal items notify the owner immediately, and remaining items batch into an end-of-day summary.

Batching inbox messages for an end-of-day summary involves routing non-urgent items into summary buckets. The triage workflow persists only these summary buckets and active wait targets to reduce state complexity while compiling remaining items for later review.

Yes, single-owner inbox workflows support asynchronous classification tasks. The process launches detached classification tasks to categorize messages and resumes the main flow when results return, enabling deterministic routing and follow-up.

Asynchronous flow resumption works by posting business messages to Slack and persisting active wait targets. The main flow pauses until replies arrive, then resumes deterministic routing to continue the inbox triage workflow.

No external dependencies are required to set up intent-based inbox routing. The workflow uses asynchronous classification tasks, flow resumption, and minimal persisted outputs like summary buckets to route messages and trigger notifications natively.

Automated inbox triage is suited for single-owner inbox workflows where messages are posted to Slack. It should be avoided for multi-owner shared inboxes or environments lacking asynchronous task support and flow resumption capabilities.