well_create_project

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

Create a project in the current workspace. A project is any tracked business object with a name, a kind and a status. Each kind has 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. Use this tool when the user asks to create, add or start tracking one of these. REQUIRED: name, kind, status. Ask the user for the kind or the status when they did not say it; never guess it. OPTIONAL: only the fields the kind takes, listed above. Dates are YYYY-MM-DD. A deal needs an amount; a non-null amount needs its currency. probability is a percentage from 0 through 100 with at most two decimals. position is a whole number from 0. billing_method (a project only) is how the work is priced: project_rate, service_rate, person_rate, fixed_fee, non_billable. parent_project_id, stage_project_id, owner_person_id, counterparty_company_id and counterparty_person_id are ids of this workspace: use one-row well_query_records lookups to resolve them; a deal takes one counterparty, a company or a contact. A field the kind does not take, or a status it does not hold, fails and nothing is written. A won or lost deal is closed on the day it is set. On WhatsApp, the person's complete typed order approves the create and writes at once. If a required value is missing, the tool returns missing_fields before any approval or write: ask for only that value, keep the same pending order and resolved ids, then call again with the answer. For a deal, ask for amount first; wait to ask for currency until the person has supplied the amount. A typed order that includes an amount without its currency asks only for the currency. Other surfaces still use their normal approval. Two live pipelines, stages of one pipeline, or cost centers of one parent cannot share a name: the call then fails, and well_list_projects finds the existing one. Returns { success: true, project } on success, { success: false, error, missing_fields } when it needs one value, or { success: false, error } on another failure.