Media Before Save for Joomla

When it runs: Before com_media saves uploaded or edited media metadata (and associated file operations).

Plugins can validate paths, resize images, or reject uploads.

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 not connected yet — flows using it will not run until JOrchestrator adds support for this Joomla hook.

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.

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

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

Before com_media saves uploaded or edited media metadata (and associated file operations).

Common patterns on the canvas:

1. Media Before Save → Send Notification (admin alert)
2. Media Before Save → Insert Row (audit log)
3. Media Before Save → 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 {{media_before_save.context}}.

Other steps in the same area of the palette:

• Media After Delete (event-onMediaAfterDelete) — Joomla Events › Media Events
• Media After Save (event-onMediaAfterSave) — Joomla Events › Media Events
• Media Before Delete (event-onMediaBeforeDelete) — Joomla Events › Media Events