Propose tasks from actionable follow-up replies
Detection half of the task conversion edge for the outbound follow-up loop. It scans data.shared watch rows written by outbound-follow-up-response-watcher, picks one response_needs_owner row whose reply needs owner action but is not a meeting request, fetches the recorded reply body, extracts one concrete owner task, and writes a durable proposal plus a notification. It never creates the task itself: the owner-invoked outbound-follow-up-create-approved-task recipe performs the write and closes the source watch row. This keeps unattended auto_run detection read/propose-only while preserving the exact reply linkage needed by the manual action.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
channels
setting
=
in_app
confidence threshold
setting
=
0.6
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.