# Content Before Delete

<!-- meta: type=event-onContentBeforeDelete; location=Joomla Events › Content Events; category=Trigger; platforms=Joomla -->

## Overview

Content Before Delete is a **Trigger** in **Joomla Events › Content Events**. Before a content-model item is deleted from the database.

Plugins can block deletion or capture data for archival. Payload includes context (entity type) and subject (the row being deleted).

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 Before Delete 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 Before Delete** to a flow:

- Automate backend work when Joomla fires `ContentBeforeDelete`
- 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

Before a content-model item is deleted from the database.

## Example workflows

Common patterns on the canvas:

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

## Good to know

General → Joomla context filter — Article limits to com_content.article. The filter is entity type, not save vs delete; this node already defines delete.

## Properties panel

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 |

### System (automatic — not edited by the user)

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 | — | — |

### User-configured — General tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `label` | Label | `text` | No | — | Node label |
| `contentContextFilter` | Joomla context filter | `content-context-filter` | No | — | Before delete — Article chip = com_content.article (articles only). Empty allows every context this generic hook receives (e.g. news feeds, redirects). Contacts, tags, and banners use their own Before/After Delete palette nodes. |

### 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_before_delete.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.title` | string | Nested field "subject.title" from this node's output payload. |
| `subject.alias` | string | Nested field "subject.alias" from this node's output payload. |
| `subject.introtext` | string | Nested field "subject.introtext" from this node's output payload. |
| `subject.fulltext` | string | Nested field "subject.fulltext" from this node's output payload. |
| `subject.catid` | number | Nested field "subject.catid" from this node's output payload. |
| `subject.state` | number | Nested field "subject.state" from this node's output payload. |
| `subject.created` | string | Nested field "subject.created" from this node's output payload. |
| `subject.created_by` | number | Nested field "subject.created_by" from this node's output payload. |
| `subject.created_user_id` | number | Nested field "subject.created_user_id" from this node's output payload. |
| `subject.modified` | string | Nested field "subject.modified" from this node's output payload. |
| `subject.modified_by` | number | Nested field "subject.modified_by" from this node's output payload. |
| `subject.modified_user_id` | number | Nested field "subject.modified_user_id" from this node's output payload. |
| `subject.created_time` | string | Nested field "subject.created_time" from this node's output payload. |
| `subject.modified_time` | string | Nested field "subject.modified_time" 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.featured` | number | Nested field "subject.featured" from this node's output 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. |

## Related nodes

Other steps in the same area of the palette:

- **Content After Delete** (`event-onContentAfterDelete`) — Joomla Events › Content Events
- **Content After Display** (`event-onContentAfterDisplay`) — Joomla Events › Content Events
- **Content After Save** (`event-onContentAfterSave`) — Joomla Events › Content Events
- **Content After Title** (`event-onContentAfterTitle`) — Joomla Events › Content Events
- **Content Before Change State** (`event-onContentBeforeChangeState`) — Joomla Events › Content Events