GEgetsales
pipeline_stages

Create pipeline stage

Add one CUSTOM stage to the end of a pipeline: type is forced to custom, key stays null (system stages exist only in the seeded default sets) and order is assigned as max+1, so sending any of the three is refused. A name colliding with a live stage of the same (team, object) is a 409 duplicate_rejected carrying existing_sid: no dedup-return, so already_exists is always false. To place it anywhere but the end, follow with update_pipeline_stage(order).

Contract:

  • MCP tool create_pipeline_stage, registry package mcp.playtables/pipeline_stages, mount playtables.pipeline.
  • Operation create, response envelope create.
  • Flags: none.
post/api/pipeline-stages

Request

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

Request body

object'person' | 'company' required

Which pipeline to append the stage to: person (leads) or company (accounts). Immutable afterwards.

namestring required

Stage label, 1..255. Must not collide with a live stage of the same (team, object), compared case-insensitively (409 duplicate_rejected, context.existing_sid).

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

Funnel bucket for the new stage. Drives the chip color and, for a person stage, what a company derives from a member sitting here.

Response

create success envelope.

successtrue required
operation'create' required
already_existsboolean required

Changes

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