# Delete Contact

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

## Overview

Deletes a contact by numeric id, {{…}} from upstream, or searchable list picker.

When the flow reaches this step, JOrchestrator executes **Delete Contact** 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 Contact is a **action step** in the **Contacts** 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 Contact** to a flow:

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

## Example workflows

Common patterns on the canvas:

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

## How to set it up

Optional deleteContactFilterCatid narrows the designer list only (does not affect runtime delete target).

## Good to know

Confirm deletion checkbox must be set when required by schema validation.

## 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 |
|--------------|-------|------|----------|--------------|-------|
| `contactId_manual` | Contact id or {{placeholder}} | `payload-text` | No | — | e.g. 42 or {{create_contact_1.id}} — or choose below (contact name appears here when using the picker) |
| `confirm` | Confirm Deletion | `checkbox` | No | — | — |

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

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `deleteContactFilterCatid` | Filter list by category (optional) | `contact-category-select` | No | — | Narrow the picker — not sent to the handler |
| `contactId` | Contact to delete | `contact-select` | No | — | Select contact (fills the line above when the id is numeric) |

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

| Field key | Type | Description |
|-----------|------|-------------|
| `id` | string | Primary record identifier. |
| `deleted` | boolean | Whether the record was deleted. |

## Related nodes

Other steps in the same area of the palette:

- **Create Contact** (`create-contact`) — Contacts
- **Create Contact Category** (`create-contact-category`) — Contacts
- **Delete Contact Category** (`delete-contact-category`) — Contacts
- **Update Contact** (`update-contact`) — Contacts
- **Update Contact Category** (`update-contact-category`) — Contacts