Delete Row is a Step (action) in Database. Deletes rows matching the specified WHERE condition.
Delete Row is a Step (action) in Database. Deletes rows matching the specified WHERE condition.
When the flow reaches this step, JOrchestrator executes Delete Row 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.
Delete Row is a action step in the Database 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 Row to a flow:
Common patterns on the canvas:
Build WHERE on the Design tab; confirm destructive runs in test environments first.
Use Select Row first to verify which rows match before deleting in production flows.
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 |
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 | — | — |
whereClause | WHERE Clause | where-clause-builder | No | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
tableName | Table Name | select (#__content | #__categories | #__users | #__usergroups | #__menu | #__modules | #__modules_menu | #__extensions | #__assets | #__languages | #__session | #__tags | #__ucm_content | #__ucm_base | #__contentitem_tag_map | #__finder_links | #__finder_terms | #__finder_tokens | #__finder_tokens_aggregate | #__finder_types | #__newsfeeds | #__overrider | #__redirect_links | #__update_sites | #__update_sites_extensions | #__updates | #__viewlevels | #__workflow_stages | #__workflow_transitions | #__workflows) | Yes | — | Select table or enter custom |
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.
After this step runs, later nodes can reference these fields using placeholders such as {{delete_row.deleted}}.
| Field key | Type | Description |
|---|---|---|
deleted | boolean | Whether the record was deleted. |
rowsAffected | number | Number of database rows affected. |
tableName | string | Database table name used by the node. |
tableName) must be filled before the flow can be saved.Other steps in the same area of the palette:
create-table) — Databaseinsert-row) — Databaseselect-row) — Databaseupdate-row) — Database