Approval-gated Quo follow-up task workflow. It reads recent conversation context for one phone number, then creates one task linked to one conversation through recued-core.quo.task.create_for_conversation. It does not send messages, delete tasks, change due dates after creation, mutate contacts, create webhooks, or call arbitrary Quo endpoints.

How it works 12 steps

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

Process (12 steps)

■ trimmed_phone_number_id trim

Trim whitespace from setting phone number id

■ trimmed_conversation_id trim

Trim whitespace from setting conversation id

■ trimmed_title trim

Trim whitespace from setting title

■ trimmed_description trim

Trim whitespace from setting description

■ has_phone_number compare

Check if trimmed phone number id has data

■ has_conversation compare

Check if trimmed conversation id has data

■ has_title compare

Check if trimmed title has data

■ has_description compare

Check if trimmed description has data

■ ready all

Check if all conditions are true

■ conversations ?

skip: step.has_phone_number not_equal true

■ create_task ?

skip: step.ready not_equal true

■ card to_summary

Format results as a summary card

Settings 7 configurable

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

quo setting =

title setting =

due date setting =

row limit setting = 10

description setting =

conversation id setting =

phone number id setting =