Contact After Save is a Trigger in Joomla Events › Contact Events. After a contact saves successfully (context com_contact.contact).
Contact After Save is a Trigger in Joomla Events › Contact Events. After a contact saves successfully (context com_contact.contact).
Contact row is persisted; use for CRM sync or notifications.
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.
Contact After 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 After Save to a flow:
ContactAfterSaveAfter a contact saves successfully (context com_contact.contact).
Common patterns on the canvas:
Context com_contact.contact only.
The designer shows these tabs for this node:
| Tab | Purpose |
|---|---|
| Info | Plain-language description and output payload fields for downstream steps |
| Design | Trigger configuration and payload schema |
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 | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
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 {{contact_after_save.context}}.
| Field key | Type | Description |
|---|---|---|
context | string | Joomla event context string. |
subject.id | number | Nested field "subject.id" from this node's output payload. |
subject.name | string | Nested field "subject.name" from this node's output payload. |
subject.alias | string | Nested field "subject.alias" from this node's output payload. |
subject.con_position | string | Nested field "subject.con_position" from this node's output payload. |
subject.address | string | Nested field "subject.address" from this node's output payload. |
subject.suburb | string | Nested field "subject.suburb" from this node's output payload. |
subject.state | string | Nested field "subject.state" from this node's output payload. |
subject.country | string | Nested field "subject.country" from this node's output payload. |
subject.postcode | string | Nested field "subject.postcode" from this node's output payload. |
subject.telephone | string | Nested field "subject.telephone" from this node's output payload. |
subject.mobile | string | Nested field "subject.mobile" from this node's output payload. |
subject.fax | string | Nested field "subject.fax" from this node's output payload. |
subject.webpage | string | Nested field "subject.webpage" from this node's output payload. |
subject.misc | string | Nested field "subject.misc" from this node's output payload. |
subject.image | string | Nested field "subject.image" from this node's output payload. |
subject.email | string | Nested field "subject.email" from this node's output payload. |
subject.email_to | string | Nested field "subject.email_to" from this node's output payload. |
subject.published | number | Nested field "subject.published" from this node's output payload. |
subject.catid | number | Nested field "subject.catid" from this node's output payload. |
subject.access | number | Nested field "subject.access" from this node's output payload. |
subject.language | string | Nested field "subject.language" from this node's output payload. |
subject.user_id | number | Nested field "subject.user_id" from this node's output payload. |
subject.created | string | Nested field "subject.created" from this node's output payload. |
subject.modified | string | Nested field "subject.modified" from this node's output payload. |
subject.metakey | string | Nested field "subject.metakey" from this node's output payload. |
subject.metadesc | string | Nested field "subject.metadesc" from this node's output payload. |
subject.subject.subject | string | Nested field "subject.subject.subject" from this node's output payload. |
subject.message | string | Nested field "subject.message" from this node's output payload. |
isNew | boolean | Boolean flag from this node's output. |
data | object | Inbound event data payload. |
audit_user.id | number | Nested field "audit_user.id" from this node's output payload. |
audit_user.username | string | Nested field "audit_user.username" from this node's output payload. |
audit_user.email | string | Nested field "audit_user.email" from this node's output payload. |
audit_user.name | string | Nested field "audit_user.name" from this node's output payload. |
audit_user.guest | boolean | Nested field "audit_user.guest" from this node's output payload. |
audit_user.client | string | Nested field "audit_user.client" from this node's output payload. |
audit_type | string | What kind of item triggered the event — for example article, category, or user. |
Other steps in the same area of the palette:
event-onContactAfterDelete) — Joomla Events › Contact Eventsevent-onContactBeforeDelete) — Joomla Events › Contact Eventsevent-onContactBeforeSave) — Joomla Events › Contact Events