tags

Short, shareable labels that mark resources (flows, errors, integrations) so teams can filter and triage them consistently.

REST API: No dedicated OpenAPI spec — see the integrator-api-specs repository for related specs. Tag references appear on other resources (notifications, flow errors) via the tagIds field.

Supports all global flags.

Subcommands

Command	Purpose
list	List every tag on the account.
get	Fetch one tag by id.
create	Create a new tag from a JSON body (--file <path> or stdin).
update	Full-replace PUT from a JSON body (--file <path> or stdin).
set	Patch fields with key=value assignments. Supports key=file://<path>.
delete	Delete a tag.

celigo tags list

List every tag. Columns: _id, tag, tagId, lastModified.

celigo tags list

Corresponds to: GET /v1/tags

celigo tags get

Fetch one tag by id.

celigo tags get <id>

Corresponds to: GET /v1/tags/{_id}

celigo tags create

Create a tag from a JSON body. Read the body from a file with -f, --file (recommended), or pipe it on stdin (--file - also means stdin). The minimal shape is {"tag":"<label>"}.

Flag	Description
-f, --file <path>	Read the JSON body from a file instead of stdin (--file - also means stdin). Added in celigo-cli 2026.6.1.

echo '{"tag":"priority"}' | celigo tags create
celigo tags create --file tag.json

Corresponds to: POST /v1/tags

celigo tags update

Full-replace PUT. Reads the complete tag document from -f, --file or stdin — omitted fields are erased.

⚠️ update replaces the entire tag. PUT erases any field you omit. GET the tag first, edit it, then send the complete document back — or use set for partial edits.

Flag	Description
-f, --file <path>	Read the JSON body from a file instead of stdin (--file - also means stdin). Added in celigo-cli 2026.6.1.
--force	Submit even if the body contains masked credential values (***) copied from a GET.

celigo tags update <id> --file tag.json
celigo tags update <id> < tag.json

Corresponds to: PUT /v1/tags/{_id}

celigo tags set

Patch individual fields with key=value assignments. Whitelisted fields are applied via an atomic PATCH; other fields go through GET → modify → PUT so omitted fields are preserved. Values are auto-parsed as JSON. A key=file://<path> value loads that field from a file instead of the command line (a leading ~ and relative paths are supported). Added in celigo-cli 2026.6.1.

celigo tags set <id> tag="Priority - triage"

Corresponds to: GET /v1/tags/{_id} then PUT /v1/tags/{_id}

celigo tags delete

Delete the tag. Prompts for confirmation unless -y is supplied.

⚠️ Deleting a tag cannot be undone. The tag is permanently removed from the account, and resources that referenced its tagId no longer resolve to it.

Flag	Description
-y, --yes	Skip confirmation.

celigo tags delete <id> -y

Corresponds to: DELETE /v1/tags/{_id}

Gotchas

• Two identifiers, two uses. _id is the Mongo id used to get, update, set, and delete the tag itself. tagId is the short human code (e.g. F3ZBQ) that other resources reference in their tagIds arrays — see flows tag-errors.
• Minimal create payload. Only tag is required; the server assigns _id and tagId. Fuller fields (color, description, etc.) vary by account and are not documented in the dist specs.

Related

• flows — flows tag-errors applies tag codes (tagId, not _id) to flow errors for triage; tags also surface on error records under a tags field.
• notifications — notification subscriptions can target tagged resources.
• integrations — integrations and their children can carry tags for search and filtering.