well_update_project

io.github.WellApp-ai/well-mcp · Verify this server

Change a project of the current workspace: its name, kind, status, dates, amount and currency, the project it nests under, for a project how its work is priced (billing_method), and for a deal its stage, owner, counterparty, win probability and position. Use this tool when the user asks to rename a project, move it to another status (for example mark a deal won or lost), move a deal to another stage, change its dates, amount, owner, counterparty or chance, set how a project is billed, or nest it under another project. Find the project_id first with a one-row well_query_records lookup. REQUIRED: project_id. OPTIONAL (only the fields the user wants changed): name, kind, status, start_date, end_date (YYYY-MM-DD), amount (a decimal string; the resulting project needs a currency), currency, parent_project_id, stage_project_id, owner_person_id, counterparty_company_id, counterparty_person_id, probability (a percentage from 0 through 100, at most two decimals), position (a whole number from 0), billing_method (a project only: project_rate, service_rate, person_rate, fixed_fee, non_billable). The ids are ids of this workspace. Use one-row well_query_records lookups to resolve them. Pass null to clear an optional field; an explicit null is a complete change. Each kind takes its own parent, statuses and fields: deal: no parent; status draft, active, paused, won, lost, archived; takes owner_person_id, counterparty_company_id, counterparty_person_id, stage_project_id, probability, position, end_date, amount, currency. pipeline: no parent; status active, archived; takes no other field. pipeline_stage: nests under a pipeline; status active, archived; takes position. cost_center: may nest under a cost_center; status active, archived; takes no other field. property: no parent; status active, archived; takes no other field. project: may nest under a project; status draft, active, paused, completed, archived; takes counterparty_company_id, counterparty_person_id, start_date, end_date, amount, currency, billing_method. campaign: no parent; status draft, active, paused, completed, archived; takes start_date, end_date. audience: no parent; status draft, active, paused, completed, archived; takes start_date, end_date. flow: no parent; status draft, active, paused, completed, archived; takes start_date, end_date. ad: may nest under a campaign; status draft, active, paused, completed, archived; takes start_date, end_date. A status moves along the kind's own path: a deal opens from draft, closes won or lost from active or paused, and a closed deal reopens to active before anything else; an archived project reopens to active. A field the kind does not take, or a move it does not allow, fails and nothing is written. A project a connected tool synced in (synced: true) keeps name, kind, parent_project_id, amount, currency, end_date, stage_project_id, owner_person_id, counterparty_company_id, counterparty_person_id from that tool: a change that names any of them fails, even beside others, and the user changes them in that tool. status, probability, position, start_date, billing_method change in Well on a synced project too. A patch is complete when it names the fields to change; do not ask for fields it leaves alone. On WhatsApp, the person's complete typed change approves and writes at once. Other surfaces still use their normal approval. Returns { success: true, project } on success, or { success: false, error } on failure.