Skip to content
Recued
Menu
← Back to recipes

Complete a Quo task

by recued-core v1

Approval-gated Quo task completion workflow. It reads one task for context, then completes that single task through recued-core.quo.task.complete. It never deletes tasks, sends messages, mutates contacts, changes phone-number settings, creates webhooks, or calls arbitrary Quo endpoints.

How it works 5 steps

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

Process (5 steps)
trimmed_task_id trim
Trim whitespace from setting task id
has_task compare
Check if trimmed task id has data
task ?
skip: step.has_task not_equal true
complete_task ?
skip: step.has_task not_equal true
card to_summary
Format results as a summary card
Settings 2 configurable

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

quo setting =
task id 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.

Permissions it requires

Read your Quo connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

quo quoopenphonebusiness-phonetaskscompletionapprovalpack:quo

Details

5 steps 2 configurable settings recipe_id: complete-quo-task