GEgetsales
pipeline_stages

Update pipeline stage

Rename, recategorize or reposition ONE stage definition; it never moves people or companies between stages (that is move_pipeline_stage_objects). order is the 1..N position and siblings recontiguate around it, which on a person pipeline also rewrites the forward-only rank the auto-advance compares. A system stage (key != null) takes name and order only: another category is a 422, and object / key are refused everywhere. Rename collision: 409; no field at all: 422 nothing_to_update.

Contract:

  • MCP tool update_pipeline_stage, registry package mcp.playtables/pipeline_stages, mount playtables.pipeline.
  • Operation update, response envelope update.
  • Flags: none.
patch/api/pipeline-stages/{sid}

Request

  • Base URL
    https://beta.getsales.io/playtables/v1
  • Auth
    HTTP bearer and API key in header Team-SID

Path parameters

sidstring required

Pipeline stage sid (cr_ps_…).

Request body

namestring

New label. A collision with another live stage of the same (team, object) is a 409 duplicate_rejected.

category'cold' | 'approaching' | 'engaging' | 'positive' | 'nurture' | 'negative' | 'disqualified'

New funnel bucket. LOCKED on a system stage (key != null): sending a different value there is a 422 validation_failed.

orderinteger

New position, 1..N within its (team, object) pipeline. Siblings recontiguate around it in the same transaction; out of range is a 422. Reordering a person pipeline changes the forward-only rank, so it changes which auto-transitions are allowed to fire.

Response

update success envelope.

successtrue required
operation'update' required
updated_fieldsstring[] required
previous_valuesobject required
kept_fieldsstring[]

The fields this write did not change because the person's own value stands on them (stamped person); read the item for what landed.

Changes

No recorded changes to this operation across all 1 revision of this API.