# Delete Menu Item

<!-- meta: type=delete-menu-item; location=Menu; category=Step (action); platforms=Joomla and WordPress (where applicable) -->

## Overview

Delete Menu Item is a **Step (action)** in **Menu**. Deletes a site menu item by alias (menu type + alias) or legacy numeric id.

When the flow reaches this step, JOrchestrator executes **Delete Menu Item** against your linked site or an external integration, using the field values you set on **General** and **Design**. Downstream steps can read the output payload fields defined for this node.

## Why use this node

Delete Menu Item is a **action step** in the **Menu** group. Action steps run in the middle or end of a flow. They perform work on your CMS, call external services, or transform data for the next step.

Typical reasons teams add **Delete Menu Item** to a flow:

- Delete Menu Item on your linked Joomla site when the flow reaches this step
- Delete menu item based on webhook, schedule, or CMS event data
- Integrate Menu operations with messaging, AI, or database steps in one canvas

## Example workflows

Common patterns on the canvas:

1. **Trigger or Webhook** → upstream steps → **Delete Menu Item** → **Send Email** or CMS update
2. **Scheduled trigger** → **Delete Menu Item** → **Debug** (while testing) → production action

## How to set it up

If the item is already gone, the node succeeds with deleted: false and not_found: true (logged in execution logs).

## Good to know

Remove child items first if Joomla blocks delete on nested menus.

## Properties panel

The designer shows these tabs for this node:

| Tab | Purpose |
|-----|---------|
| **Info** | Plain-language description and output payload fields for downstream steps |
| **General** | Canvas label and read-only node ID |
| **AI** | Optional assistant to help draft settings from plain language |
| **Design** | Node-specific configuration fields |

### 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 | — | — |
| `_payloadFields` | Available Fields | `payload-panel` | No | — | — |

### User-configured — General tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `label` | Label | `text` | No | — | Node label |

### User-configured — Design tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `confirm` | Confirm deletion | `checkbox` | No | — | — |

### CMS-backed (options from the linked site)

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `menuType` | Menu | `menu-type-select` | **Yes** | — | Select menu |
| `alias` | Menu item to delete | `menu-item-select` | **Yes** | — | Select item |

### 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
`{{delete_menu_item.id}}`.

| Field key | Type | Description |
|-----------|------|-------------|
| `id` | string | Primary record identifier. |
| `alias` | string | URL-safe alias / slug. |
| `deleted` | boolean | Whether the record was deleted. |
| `not_found` | boolean | Boolean flag from this node's output. |
| `message` | string | Human-readable status, error, or result summary. |

## Related nodes

Other steps in the same area of the palette:

- **Create Menu Item** (`create-menu-item`) — Menu
- **Update Menu Item** (`update-menu-item`) — Menu