Node reference

Content After Save for Joomla

Starts Joomla automation when an article (or other content item) finishes saving — the onContentAfterSave hook. Use it instead of a content plugin to notify, sync, or continue a…

Overview

Starts Joomla automation when an article (or other content item) finishes saving — the onContentAfterSave hook. Use it instead of a content plugin to notify, sync, or continue a workflow after Joomla persists the record.

Typical hook for sync, notifications, or workflows tied to created/updated items (articles by default).

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 when Platform Events are turned on in Joomla (System → JOrchestrator) and matching flows are set to Active.

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

Content After Save is a trigger in the Joomla Events › Content 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 Content After Save to a flow:

  • Run Joomla workflow automation when an article is created or updated
  • Notify editors or Slack without a custom onContentAfterSave plugin
  • Sync the saved item to a CRM, sheet, or search index
  • Branch on featured/state and only continue when the article should go further

When it runs

After a content-model save succeeds and the record is persisted.

Example workflows

Common patterns on the canvas:

  1. Content After Save → Send Notification (admin alert)
  2. Content After Save → Insert Row (audit log)
  3. Content After Save → If → Send Email / Update Article

Good to know

General → Joomla context filter — com_content.article for article saves 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
labelLabeltextNo—Node label
contentContextFilterJoomla context filtercontent-context-filterNo—After DB write — com_content.article for article saves only.

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

Field keyTypeDescription
contextstringJoomla event context string.
subject.idnumberNested field "subject.id" from this node's output payload.
subject.titlestringNested field "subject.title" from this node's output payload.
subject.aliasstringNested field "subject.alias" from this node's output payload.
subject.introtextstringNested field "subject.introtext" from this node's output payload.
subject.fulltextstringNested field "subject.fulltext" from this node's output payload.
subject.catidnumberNested field "subject.catid" from this node's output payload.
subject.statenumberNested field "subject.state" from this node's output payload.
subject.createdstringNested field "subject.created" from this node's output payload.
subject.created_bynumberNested field "subject.created_by" from this node's output payload.
subject.created_user_idnumberNested field "subject.created_user_id" from this node's output payload.
subject.modifiedstringNested field "subject.modified" from this node's output payload.
subject.modified_bynumberNested field "subject.modified_by" from this node's output payload.
subject.modified_user_idnumberNested field "subject.modified_user_id" from this node's output payload.
subject.created_timestringNested field "subject.created_time" from this node's output payload.
subject.modified_timestringNested field "subject.modified_time" 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.featurednumberNested field "subject.featured" from this node's output payload.
isNewbooleanBoolean flag from this node's output.
data.idnumberNested field "data.id" from this node's output payload.
data.titlestringNested field "data.title" from this node's output payload.
data.aliasstringNested field "data.alias" from this node's output payload.
data.introtextstringNested field "data.introtext" from this node's output payload.
data.fulltextstringNested field "data.fulltext" from this node's output payload.
data.catidnumberNested field "data.catid" from this node's output payload.
data.statenumberNested field "data.state" from this node's output payload.
data.createdstringNested field "data.created" from this node's output payload.
data.created_bynumberNested field "data.created_by" from this node's output payload.
data.created_user_idnumberNested field "data.created_user_id" from this node's output payload.
data.modifiedstringNested field "data.modified" from this node's output payload.
data.modified_bynumberNested field "data.modified_by" from this node's output payload.
data.modified_user_idnumberNested field "data.modified_user_id" from this node's output payload.
data.created_timestringNested field "data.created_time" from this node's output payload.
data.modified_timestringNested field "data.modified_time" from this node's output payload.
data.accessnumberNested field "data.access" from this node's output payload.
data.languagestringNested field "data.language" from this node's output payload.
data.featurednumberNested field "data.featured" from this node's output 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.