# Update Tag

<!-- meta: type=update-tag; location=Tags; category=Step (action); platforms=Joomla and WordPress (where applicable) -->

## Overview

Update Tag is a **Step (action)** in **Tags**. Updates an existing tag's title and publishing fields.

When the flow reaches this step, JOrchestrator executes **Update Tag** against your linked site or an external integration, using the field values you set on **General** and **Design**. Downstream steps can read the output payload fields defined for this node.

## Why use this node

Update Tag is a **action step** in the **Tags** group. Action steps run in the middle or end of a flow. They perform work on your CMS, call external services, or transform data for the next step.

Typical reasons teams add **Update Tag** to a flow:

- Update Tag on your linked Joomla site when the flow reaches this step
- Update tag based on webhook, schedule, or CMS event data
- Integrate Tags operations with messaging, AI, or database steps in one canvas

## Example workflows

Common patterns on the canvas:

1. **Trigger or Webhook** → upstream steps → **Update Tag** → **Send Email** or CMS update
2. **Scheduled trigger** → **Update Tag** → **Debug** (while testing) → production action

## How to set it up

Pick the tag from Joomla on Design — not a raw id text field.

## Good to know

Changing title does not automatically retag articles — use article nodes for associations.

## Properties panel

The designer shows these tabs for this node:

| Tab | Purpose |
|-----|---------|
| **Info** | Plain-language description and output payload fields for downstream steps |
| **General** | Canvas label and read-only node ID |
| **AI** | Optional assistant to help draft settings from plain language |
| **Design** | Node-specific configuration fields |

### System (automatic — not edited by the user)

These fields are managed by the designer or runtime — you do not type into them directly:

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `_nodeId` | Node ID | `node-id` | No | — | — |
| `_payloadFields` | Available Fields | `payload-panel` | No | — | — |

### User-configured — General tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `label` | Label | `text` | No | — | Node label |

### User-configured — Design tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `value` | Title | `payload-text` | No | — | Tag title or drag payload field |
| `published` | Published | `select` (`0` \| `1` \| `2` \| `-2`; default: `1`) | No | — | — |

### CMS-backed (options from the linked site)

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `id` | Tag to update | `tag-select` | **Yes** | — | Select tag |
| `language` | Language | `content-language-select` | No | — | Select language (* = all) |

### CMS site configuration (not on this node's properties panel)

Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under **Node Configuration**, not per step on this node. Link the flow to a domain before testing CMS-backed fields.

## Output payload fields

After this step runs, later nodes can reference these fields using placeholders such as
`{{update_tag.id}}`.

| Field key | Type | Description |
|-----------|------|-------------|
| `id` | string | Primary record identifier. |
| `title` | string | Title text for the created or updated record. |
| `alias` | string | URL-safe alias / slug. |

## Related nodes

Other steps in the same area of the palette:

- **Create Tag** (`create-tag`) — Tags
- **Create Tag** (`wp-create-tag`) — Tags
- **Delete Tag** (`delete-tag`) — Tags
- **Delete Tag** (`wp-delete-tag`) — Tags
- **Instagram Account Info** (`instagram-account-info`) — Tags