Node reference

Contact Before Save for Joomla

When it runs: Before a contact is saved in com_contact (onContentBeforeSave with context com_contact.contact).

Overview

When it runs: Before a contact is saved in com_contact (onContentBeforeSave with context com_contact.contact).

Plugins can modify contact table data or block save.

Each run also includes who was logged in at the time and what kind of item was involved — see audit_user and audit_type in Payload Fields below.

This trigger is active for the content types listed in its context filter — use the General tab to limit which items start the flow.

When this trigger fires, JOrchestrator starts the flow and passes the incoming event or request data to the next connected step. Configure filtering, payload shape, and security on the Design tab.

Why use this node

Contact Before Save is a trigger in the Joomla Events › Contact Events group. Triggers start a flow. They listen for an external signal — a CMS event, inbound HTTP call, payment notification, or schedule — and pass the incoming data to the first downstream step.

Typical reasons teams add Contact Before Save to a flow:

  • Automate backend work when Joomla fires ContactBeforeSave
  • Notify administrators or sync external systems on this CMS lifecycle event
  • Enrich or validate CMS data before it is persisted
  • Audit user, content, or extension activity without custom plugins

When it runs

Before a contact is saved in com_contact (onContentBeforeSave with context com_contact.contact).

Example workflows

Common patterns on the canvas:

  1. Contact Before SaveSend Notification (admin alert)
  2. Contact Before SaveInsert Row (audit log)
  3. Contact Before SaveIfSend Email / Update Article

Good to know

Context com_contact.contact only.

Properties panel

The designer shows these tabs for this node:

TabPurpose
InfoPlain-language description and output payload fields for downstream steps
DesignTrigger configuration and payload schema

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

User-configured — General tab

Property keyLabelTypeRequiredVisible whenNotes
labelLabeltextNoNode label

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 {{contact_before_save.context}}.

Field keyTypeDescription
contextstringJoomla event context string.
subject.idnumberNested field "subject.id" from this node's output payload.
subject.namestringNested field "subject.name" from this node's output payload.
subject.aliasstringNested field "subject.alias" from this node's output payload.
subject.con_positionstringNested field "subject.con_position" from this node's output payload.
subject.addressstringNested field "subject.address" from this node's output payload.
subject.suburbstringNested field "subject.suburb" from this node's output payload.
subject.statestringNested field "subject.state" from this node's output payload.
subject.countrystringNested field "subject.country" from this node's output payload.
subject.postcodestringNested field "subject.postcode" from this node's output payload.
subject.telephonestringNested field "subject.telephone" from this node's output payload.
subject.mobilestringNested field "subject.mobile" from this node's output payload.
subject.faxstringNested field "subject.fax" from this node's output payload.
subject.webpagestringNested field "subject.webpage" from this node's output payload.
subject.miscstringNested field "subject.misc" from this node's output payload.
subject.imagestringNested field "subject.image" from this node's output payload.
subject.emailstringNested field "subject.email" from this node's output payload.
subject.email_tostringNested field "subject.email_to" from this node's output payload.
subject.publishednumberNested field "subject.published" from this node's output payload.
subject.catidnumberNested field "subject.catid" from this node's output payload.
subject.accessnumberNested field "subject.access" from this node's output payload.
subject.languagestringNested field "subject.language" from this node's output payload.
subject.user_idnumberNested field "subject.user_id" from this node's output payload.
subject.createdstringNested field "subject.created" from this node's output payload.
subject.modifiedstringNested field "subject.modified" from this node's output payload.
subject.metakeystringNested field "subject.metakey" from this node's output payload.
subject.metadescstringNested field "subject.metadesc" from this node's output payload.
subject.subject.subjectstringNested field "subject.subject.subject" from this node's output payload.
subject.messagestringNested field "subject.message" from this node's output payload.
isNewbooleanBoolean flag from this node's output.
dataobjectInbound event data payload.
audit_user.idnumberNested field "audit_user.id" from this node's output payload.
audit_user.usernamestringNested field "audit_user.username" from this node's output payload.
audit_user.emailstringNested field "audit_user.email" from this node's output payload.
audit_user.namestringNested field "audit_user.name" from this node's output payload.
audit_user.guestbooleanNested field "audit_user.guest" from this node's output payload.
audit_user.clientstringNested field "audit_user.client" from this node's output payload.
audit_typestringWhat kind of item triggered the event — for example article, category, or user.