Node reference

Create Contact Category for Joomla

Create Contact Category is a Step (action) in Contacts. Creates a contact category (#__categories with extension com_contact).

Overview

Create Contact Category is a Step (action) in Contacts. Creates a contact category (#__categories with extension com_contact).

When the flow reaches this step, JOrchestrator executes Create Contact 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 Contact Category is a action step in the Contacts 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 Contact Category to a flow:

  • Create Contact Category on your linked Joomla site when the flow reaches this step
  • Create contact category based on webhook, schedule, or CMS event data
  • Integrate Contacts operations with messaging, AI, or database steps in one canvas

Example workflows

Common patterns on the canvas:

  1. Trigger or Webhook → upstream steps → Create Contact CategorySend Email or CMS update
  2. Scheduled triggerCreate Contact CategoryDebug (while testing) → production action

How to set it up

Title and optional parent, alias, description on Design.

Good to know

After the run, id is the category id for downstream Create Contact nodes. Returns existing id if an identical category already exists.

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
labelLabeltextNoNode label

User-configured — Design tab

Property keyLabelTypeRequiredVisible whenNotes
titleCategory TitletextYesTitle or {{placeholder}}
aliasAlias (optional)textNoURL segment; auto from title if empty
descriptionDescriptiontextareaNoCategory description

CMS-backed (options from the linked site)

Property keyLabelTypeRequiredVisible whenNotes
parentParent categorycontact-category-selectNoSelect parent (contact 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_contact_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.