Node reference

Create Category for Joomla

Creates a Joomla category from workflow data so later Create Article steps have somewhere to land.

Overview

Creates a Joomla category from workflow data so later Create Article steps have somewhere to land.

When the flow reaches this step, JOrchestrator executes Create 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.

Why use this node

Create 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 Create Category to a flow:

  • Provision categories when a new client site or campaign starts
  • Mirror an external taxonomy into Joomla without a CLI script
  • Create the category, then immediately create articles underneath it

Example workflows

Common patterns on the canvas:

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

How to set it up

Title required; alias optional (auto-generated from title if empty).

Good to know

Returns the new category id for downstream Create Article nodes.

Properties panel

The designer shows these tabs for this node:

TabPurpose
InfoPlain-language description and output payload fields for downstream steps
GeneralCanvas label and read-only node ID
AIOptional assistant to help draft settings from plain language
DesignNode-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 keyLabelTypeRequiredVisible whenNotes
_nodeIdNode IDnode-idNo——
_payloadFieldsAvailable Fieldspayload-panelNo——

User-configured — General tab

Property keyLabelTypeRequiredVisible whenNotes
labelLabeltextNo—Node label

User-configured — Design tab

Property keyLabelTypeRequiredVisible whenNotes
titleCategory TitletextYes—Title or {{placeholder}}
aliasAlias (optional)textNo—URL segment; auto from title if empty
descriptionDescriptiontextareaNo—Category description

CMS-backed (options from the linked site)

Property keyLabelTypeRequiredVisible whenNotes
parentParent Categorycategory-selectNo—Select parent (article categories)

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 {{create_category.id}}.

Field keyTypeDescription
idstringPrimary record identifier.
titlestringTitle text for the created or updated record.
aliasstringURL-safe alias / slug.
parent_idstringParent category or menu item ID.
descriptionstringCategory or contact description text.
pathstringFilesystem-relative path (often under /images).
levelnumberNesting level in the category tree.
already_existedbooleanTrue when create found an existing record instead of creating.

Validation rules

  • Category Title (title) must be filled before the flow can be saved.