createTaskLabel

mutation · in the family Task label

What it does

Create a new label for organizing tasks at your organization.

Create a TaskLabel in the caller's org group. Template class (org & group operational structure — vocabulary curation is management work; hand-derived v29).

Who may call it

Capability area: Places and layout — How your organizations and facilities are arranged day to day — facilities, zones and bins, teams and labels.

Owner
System Administrator
Manager
An API key whose scope allows api:createTaskLabel

Arguments

Name	Type	Required	Notes
`input`	NewTaskLabelInput `NewTaskLabelInput!`	yes	No further notes.

Returns

TaskLabel TaskLabel! — A TaskLabel — the WORK vocabulary: a group-defined label attached to Tasks by reference (labelIds). DELIBERATELY its OWN master, NOT a reuse of the catalog Tag — catalog vocabulary (what we sell) and work vocabulary (how we operate) must not blend, and dooming a work label must never referential-gate against catalog nodes. The Tag SHAPE otherwise (caption + optional #rrggbb color; free-string labels stay unrepresentable — typo-proof, rename-safe via caption). FSM: active(i) ⇄ inactive → doomed (the template — ≠ the Tag's two-state: work vocabulary retires seasonally and comes back, so inactive earns its keep; 'blocked' lives HERE as a label because it has no machine consequence — the disclosed states-vs-labels lean). NOT searchable (supporting vocabulary — the Decoration SB-d class; reached via the tasks list filter, never name-found). The ops event domain (at.ops.task_label.*).

Example request

mutation ExampleCreateTaskLabel($input: NewTaskLabelInput!) {
  createTaskLabel(input: $input) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    color
  }
}

Variables:

{
  "input": {
    "caption": "Blue jeans"
  }
}

Send it with the envelope naming the version: "extensions": {"at": {"version": {"name":"genesis","number":0}}}.

Example response

{
  "data": {
    "createTaskLabel": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "LB-EXMP-0000-000F",
      "type": "TaskLabel",
      "caption": "Blue jeans",
      "status": "active",
      "parentId": "01900000-0000-7000-8000-065235280000",
      "rootId": "01900000-0000-7000-8000-a093dd800000",
      "createdAt": "2027-01-31T00:00:00.000Z",
      "updatedAt": "2027-01-31T00:00:00.000Z",
      "revisionNum": 1,
      "revision": "01900000-0000-7000-8000-b7960e180000",
      "color": "<color>"
    }
  },
  "extensions": {
    "at": {
      "callId": "01EXAMPLE-CALL-ID",
      "version": {
        "requested": {
          "name": "genesis",
          "number": 0
        },
        "serviced": {
          "name": "genesis",
          "number": 0
        }
      }
    }
  }
}

Errors this call can answer

VALIDATION/INVALID — Something in the request is not valid. (VALIDATION)
AUTHN/REQUIRED — Sign in to do this. (AUTHN)
AUTHZ/FORBIDDEN — Your role does not allow this action. (AUTHZ)
RATE_LIMIT/THROTTLED — Too many requests in a short time. (RATE_LIMIT)
CONFLICT/* — The record’s state, or a change made in the meantime, does not allow this; the codes are on the CONFLICT page. (CONFLICT)
VALIDATION/VERSION_REQUIRED — The request did not say which app version it came from. (VALIDATION)

Dry run

Add dryRun: true to the request envelope (extensions.at) to rehearse this call: every check runs, the write is rehearsed against the current records and nothing is stored; the answer is the refusal a real call would give, or the record it would create. Every response to a rehearsal carries dryRun: true, so a rehearsed record is never mistaken for a saved one.

Used in

Give the team its work — tasks, labels, hand-offs