# Content Before Change State

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

## Overview

When it runs: Before published/unpublished/archived/trashed state is changed on selected content-model rows (typical source: admin list checkboxes).

Joomla passes context, subject (array of row IDs only — not title, body, or a content object), and value (new state). Plugins can veto the change.

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 Change State 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 Change State** to a flow:

- Automate backend work when Joomla fires `ContentBeforeChangeState`
- 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 published/unpublished/archived/trashed state is changed on selected content-model rows (typical source: admin list checkboxes).

## Example workflows

Common patterns on the canvas:

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

## Good to know

General → Joomla context filter — Article limits to com_content.article. For one ID use {{nodeId.subject.0}} or Iterator on {{nodeId.subject}}. For an API body, pass the whole list as {{nodeId.subject}} in Raw JSON (unquoted), not as object-shaped rows.

## 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 state change — subject is an array of row IDs (not full records). Article chip = com_content.article. |

### 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_change_state.context}}`.

| Field key | Type | Description |
|-----------|------|-------------|
| `context` | string | Joomla event context string. |
| `subject` | array | Email or notification subject line. |
| `subject.0` | number | Nested field "subject.0" from this node's output payload. |
| `value` | number | New state value for change-state events. |
| `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 Delete** (`event-onContentBeforeDelete`) — Joomla Events › Content Events