Detection half of the core mail-to-task loop. It fires when a mail record is created, applies deterministic subject/sender allow and block filters before any body read or AI call, extracts one concrete owner task only for matched mail, writes a small awaiting_owner_approval proposal row in data.shared, and notifies the owner. It defaults to requiring at least one allow filter so large inboxes do not burn model tokens by default. It never creates the task itself: the owner-invoked create-approved-mail-task recipe performs the Recued task write.
Mail Task Proposal Loop
Core-only workflow pack for turning filtered inbound mail into Recued tasks. The producer is fail-closed by default until the owner configures subject or sender allow terms; matching mail is then read, extracted into one likely owner task, and persisted only as a small proposal ledger row in data.shared. The manual recipe creates the Recued task after the owner chooses to run it. This pack does not send email, depend on an external work tracker, create vendor tasks, or replace the inbox: it adds a deterministic filter and approval step between email and Recued-native work.
What this pack installs
Included recipes
2 pinned recipes
This pack installs the complete recipe workflow together. 1 supporting recipe runs as background automation.
Owner-invoked create half of the core mail-to-task loop. It reads one awaiting_owner_approval proposal written by mail-task-proposal-producer, optionally targeted by proposal_thread_key, creates a Recued task from the proposal, links the task back to the source mail record, and marks the proposal created. This recipe is manual-only: running it is the owner's approval to turn the proposed mail action into durable Recued work.
Builds on
Trust & control
What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.