Workflow origin for the Google Tasks task closure loop. It reads one task list for context, creates exactly one owner-approved active Google Task through recued-core.google-tasks.task.create, and when the task succeeds it seeds durable data.shared closure state for google-task-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not complete, update, delete, move, reorder, rename lists, mutate links, touch hidden/deleted or assignment-source fields, clear completed tasks, or otherwise mutate Google Tasks beyond the approved task create.
Create Google Task with closure watch
Workflow origin for the Google Tasks task closure loop. It reads one task list for context, creates exactly one owner-approved active Google Task through recued-core.google-tasks.task.create, and when the task succeeds it seeds durable data.shared closure state for google-task-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not complete, update, delete, move, reorder, rename lists, mutate links, touch hidden/deleted or assignment-source fields, clear completed tasks, or otherwise mutate Google Tasks beyond the approved task create.
Complete workflow
Google Tasks Task Closure Loop
4 pinned recipes
Workflow pack for Recued-created Google Tasks tasks. It composes the Google Tasks capability pack with a closure ledger: create one owner-approved active task in an existing task list, persist only the connection/list/task linkage in data.shared, and let a scheduled watcher re-read that exact task until Google Tasks reports completion. This pack does not replace Google Tasks due dates, reminders, list organization, task moves, assignment-source behavior, hidden/deleted task handling, clear-completed cleanup, daily planning, or general task dashboards; it adds Recued-visible closure state for Google Tasks tasks Recued created.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Scheduled adopter for Google Tasks task closure rows seeded by create-google-task-with-closure. It lists only Recued-originated Google Task watches, re-reads a bounded batch of Google Task, and closes the shared row when Google Tasks reports completion. Rows that cannot be read remain open instead of closing from cached state. It can notify the owner on completion, but it never creates, updates, completes, deletes, moves, reorders, renames lists, mutates links, touches hidden/deleted or assignment-source fields, clears completed tasks, or otherwise mutates Google Tasks.
Low-frequency timeout role for recued-core/google-tasks-task-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.
Owner-visible list/close role for recued-core/google-tasks-task-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (39 steps)
tasklist_id_value
trim
Trim whitespace from setting tasklist id
task_title_value
trim
Trim whitespace from setting task title
notes_value
trim
Trim whitespace from setting notes
due_value
trim
Trim whitespace from setting due
has_connection
compare
Check if setting google has data
has_tasklist_id
compare
Check if tasklist id value has data
has_task_title
compare
Check if task title value has data
has_due
compare
Check if due value has data
skip_task_list_read
any
Check if any of the conditions are true
task_list
?
skip: step.skip_task_list_read equal true
live_tasklist_id
default
Apply default
has_live_task_list
compare
Check if live tasklist id has data
skip_task_create
any
Check if any of the conditions are true
skip_dated_task_create
any
Check if any of the conditions are true
create_dated_task
?
skip: step.skip_dated_task_create equal true
skip_undated_task_create
any
Check if any of the conditions are true
create_undated_task
?
skip: step.skip_undated_task_create equal true
created_task
ternary
Apply ternary
created_task_id
default
Apply default
has_created_task
compare
Check if created task id has data
created_status
default
Apply default
created_status_norm
lowercase
Convert created status to lowercase
created_task_completed
compare
Check if created status norm equals completed
created_at
date_add
Add 0 days to
raw_task_key
join
Join items with ":"
task_key_colon
replace
Replace text in raw task key
task_key_slash
replace
Replace text in task key colon
task_key_dot
replace
Replace text in task key slash
task_key_at
replace
Replace text in task key dot
task_key_space
replace
Replace text in task key at
task_key_left_angle
replace
Replace text in task key space
task_key_right_angle
replace
Replace text in task key left angle
task_key_plus
replace
Replace text in task key right angle
task_key_equals
replace
Replace text in task key plus
task_key_question
replace
Replace text in task key equals
skip_closure_seed
any
Check if any of the conditions are true
closure_timeout_at
date_add
Add setting no response timeout days days to
seed_google_task_closure_watch
?
skip: step.skip_closure_seed equal true
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
due
setting
=
notes
setting
=
google
setting
=
task title
setting
=
tasklist id
setting
=
@default
no response timeout days
setting
=
30
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.