Updates a Joomla article category (title, parent, alias, description) when the flow runs. Use to reorganize taxonomy after imports, rename sections, or sync category metadata fr…
Updates a Joomla article category (title, parent, alias, description) when the flow runs. Use to reorganize taxonomy after imports, rename sections, or sync category metadata from an external PIM.
When the flow reaches this step, JOrchestrator executes Update Category 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.
Update Category is a action step in the Categories 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 Category to a flow:
Common patterns on the canvas:
Select the category on Design; optional new title, parent, alias, and description fields.
Cannot move a category under its own descendant — Joomla enforces the tree.
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 |
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 | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
title | New title (optional) | text | No | — | Leave blank to keep |
alias | Alias (optional) | text | No | — | Leave blank to keep or regenerate |
description | Description (optional) | textarea | No | — | Leave blank to keep |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
id | Category | category-select | Yes | — | Category to update |
parent | New parent (optional) | category-select | No | — | Leave unchanged if not set |
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.
After this step runs, later nodes can reference these fields using placeholders such as {{update_category.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. |
parent_id | string | Parent category or menu item ID. |
description | string | Category or contact description text. |
path | string | Filesystem-relative path (often under /images). |
level | number | Nesting level in the category tree. |
Other steps in the same area of the palette:
create-category) — Categorieswp-create-category) — Categoriesdelete-category) — Categorieswp-delete-category) — Categorieswp-update-category) — Categories