taskflow-inbox-triage

Inbox triage automation uses a single-owner flow that classifies incoming items by intent and routes actions automatically, defers them for external input, or summarizes unresolved items at day end.

Workflow state management uses stateJson to track classification and waitJson to set a waiting state, pausing the flow until external input arrives, then resuming and finishing the flow automatically.

Yes, you can generate end-of-day summaries by routing unresolved inbox items to a summary task within the triage flow, ensuring deferred or unclassified messages are collected for later follow-up.

The best way to handle single-owner inbox routing is applying a classification task that evaluates message intent and directs items to immediate notifications, waiting states, or end-of-day summaries based on the result.

Yes, the inbox triage pattern supports pausing and resuming workflows by setting a waiting state with waitJson, then automatically resuming the flow when the required external input arrives.