Skip to content
Recued
Menu
← Back to recipes

Create approved mail task

by recued-core v1

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.

Complete workflow

Mail Task Proposal Loop 2 pinned recipes

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.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

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.

emailmailtaskwork-entity
by recued-core pinned v1
Propose Recued tasks from mail
Background automation

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.

emailmailtaskwork-entity
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 37 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Data fetch
proposals ?
Process (36 steps)
proposals_family filter
Filter by condition
pending_proposals filter
Filter by condition
has_target compare
Check if setting proposal thread key has data
targeted_proposals filter
Filter by condition
selected_pool ternary
Apply ternary
candidate_proposals slice
Take a subset of
pending_count count
Count items in pending proposals
has_candidate compare
Check if candidate proposals has data
proposal_key default
Apply default
mail_slug default
Apply default
record_id default
Apply default
thread_id default
Apply default
thread_key default
Apply default
subject default
Apply default
from_email default
Apply default
task_title_raw default
Apply default
task_title trim
Trim whitespace from task title raw
task_notes default
Apply default
due_at default
Apply default
raw_priority default
Apply default
priority_is_low compare
Check if raw priority equals low
priority_is_high compare
Check if raw priority equals high
priority_high_or_medium ternary
Apply ternary
task_priority ternary
Apply ternary
extraction_confidence default
Apply default
has_mail_slug compare
Check if mail slug has data
has_record_id compare
Check if record id has data
has_thread_id compare
Check if thread id has data
has_task_title compare
Check if task title has data
skip_create any
Check if any of the conditions are true
task_created ?
skip: step.skip_create equal true
has_task compare
Check if task created task id has data
skip_finalize any
Check if any of the conditions are true
mark_proposal_created ?
skip: step.skip_finalize equal true
link_task_to_mail ?
skip: step.skip_finalize equal true
card to_summary
Format results as a summary card
Settings 2 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

container names setting = [object Object]
proposal thread key setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Data it touches

Warehousedata.taskdata.maildata.shared

About

Tags

emailmailtaskwork-entityapprovalclosed-loopcore-onlystate:mail-task-proposal-producerpack:mail-task-proposal

Details

37 steps 2 configurable settings recipe_id: create-approved-mail-task