Updates an existing Joomla contact record (com_contact) when the flow runs. Use to sync CRM changes, fix details after form submissions, or batch-update contact categories.
Updates an existing Joomla contact record (com_contact) when the flow runs. Use to sync CRM changes, fix details after form submissions, or batch-update contact categories.
When the flow reaches this step, JOrchestrator executes Update Contact 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 Contact 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 Update Contact to a flow:
Common patterns on the canvas:
Pick the contact from the Joomla list. To change category: id / {{…}} and/or Contact Categories; leave manual and picker empty to keep current category.
Name and slug fields follow com_contact validation rules.
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 |
|---|---|---|---|---|---|
name | Name | payload-text | No | — | Leave empty to keep current |
catid_manual | Contact category (id or {{placeholder}}) — optional | payload-text | No | — | Leave empty to keep category; or type id / {{…}} — or choose below (shows category name) |
alias | Alias | payload-text | No | — | — |
published | Published | select (` | 0 | 1; default: `) | No | — | — |
email_to | Contact email | payload-text | No | — | — |
address | Address | payload-text | No | — | — |
suburb | City / Suburb | payload-text | No | — | — |
state | State / County | payload-text | No | — | — |
postcode | Postal code | payload-text | No | — | — |
country | Country | payload-text | No | — | — |
telephone | Telephone | payload-text | No | — | — |
mobile | Mobile | payload-text | No | — | — |
webpage | Website | payload-text | No | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
id | Contact to update | contact-select | Yes | — | Select contact from Joomla |
catid | Contact Categories (optional) | contact-category-select | No | — | Select category (fills the field above) |
language | Language | content-language-select | No | — | Select language (* = all) |
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_contact.id}}.
| Field key | Type | Description |
|---|---|---|
id | string | Primary record identifier. |
name | string | Display name of the record. |
alias | string | URL-safe alias / slug. |
catid | string | Category ID. |
published | number | Published flag (0 or 1). |
email_to | string | Contact form recipient email. |
Other steps in the same area of the palette:
create-contact) — Contactscreate-contact-category) — Contactsdelete-contact) — Contactsdelete-contact-category) — Contactsupdate-contact-category) — Contacts