Node reference

Insert Row for Joomla and WordPress

Inserts a row into a connected table or sheet from the flow. Use it as an audit log for Joomla events and WordPress hooks.

Overview

Inserts a row into a connected table or sheet from the flow. Use it as an audit log for Joomla events and WordPress hooks.

When the flow reaches this step, JOrchestrator executes Insert 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.

Why use this node

Insert 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 Insert Row to a flow:

Log every Content After Save or save_post for reporting
Store webhook payloads before you act on them
Keep an operations trail without a custom logger plugin

Example workflows

Common patterns on the canvas:

Trigger or Webhook → upstream steps → Insert Row → Send Email or CMS update
Scheduled trigger → Insert Row → Debug (while testing) → production action

How to set it up

Map column values from upstream payload fields or enter literals on the Design tab.

Good to know

Connect downstream of a node that defines table name or row data when using dynamic tables.

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	—	—
`columnData`	Column Values	`column-inputs`	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
`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

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 {{insert_row.insertedRow}}.

Field key	Type	Description
`insertedRow`	object	Object representing the inserted row.
`insertedId`	string	ID of the newly inserted row.
`tableName`	string	Database table name used by the node.

Validation rules

Table Name (tableName) must be filled before the flow can be saved.