Node reference

Cache Get for Joomla

When it runs: Each time Joomla reads a value from cache (Cache::get), which can happen many times per request.

Node reference

Overview

When it runs: Each time Joomla reads a value from cache (Cache::get), which can happen many times per request.

Indicates a cache lookup; high volume on busy sites.

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

Cache Get is a trigger in the Joomla Events › Cache 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 Cache Get to a flow:

  • Automate backend work when Joomla fires CacheGet
  • 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

Each time Joomla reads a value from cache (Cache::get), which can happen many times per request.

Example workflows

Common patterns on the canvas:

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

Good to know

JOrchestrator caps dispatches per request (plugin setting max_cache_get_per_request).

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

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 {{cache_get.key}}.

Field keyTypeDescription
keystringText value from this node's output.
groupstringText value from this node's output.
resultstringBoolean result of the condition evaluation.
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.