Skip to content
Routario Docs

Propose change

Module · Stable

Propose a CRM deal-graph change for a person to review, instead of applying it directly.

Writes a pending proposal to the review queue (the /deals/proposals review surface and the inbox) instead of changing the deal graph directly. ‘change’ picks what to propose: attach_note (needs note_text + deal_id or contact_id), create_deal (needs deal_name + contact_id), change_stage (needs deal_id + to_stage_name), or create_task (needs task_title + deal_id or contact_id). A person accepts or dismisses each proposal; accepting materialises the real change. Pass source_ref (e.g. ‘memory_item::propose::<deal_id>’) to make repeat calls for the same source return the existing proposal instead of raising a second identical one in the review queue.

When to use

Section titled “When to use”

Use when an agent or flow should SUGGEST a deal-graph change for a person to confirm — the ‘AI proposes, the user curates’ pattern. Grant this to a configured agent in place of the direct crm_* skills when you want a human review step before anything is written.

When not to use

Section titled “When not to use”

If the change should be applied immediately with no review, use the direct skills instead (Create Deal, Add Note, Move Deal Stage, Create Task). Proposals for non-deal substrate kinds do not materialise yet — use the matching direct skill for those.

Inputs

Section titled “Inputs”

Configured per use: change, deal_id, contact_id, deal_name, to_stage_name, note_text, task_title, reason, source_ref.

Outputs

Section titled “Outputs”
  • proposal_id
  • change
  • target_kind
  • status

Auto-generated from the skill registry (load_skills()). Do not edit by hand.