Cache Remove for Joomla

Cache Remove is a Trigger in Joomla Events › Cache Events. When a specific cache entry is removed (Cache::remove).

Targeted invalidation of one key in a cache group.

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.

Cache Remove 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 Remove to a flow:

• Automate backend work when Joomla fires CacheRemove
• 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 a specific cache entry is removed (Cache::remove).

Common patterns on the canvas:

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

The designer shows these tabs for this node:

After this step runs, later nodes can reference these fields using placeholders such as {{cache_remove.key}}.

Other steps in the same area of the palette:

• Cache Clear (event-onCacheClear) — Joomla Events › Cache Events
• Cache Get (event-onCacheGet) — Joomla Events › Cache Events
• Cache Store (event-onCacheStore) — Joomla Events › Cache Events