Node reference

Custom Table for Joomla and WordPress

Custom Table is a Step (action) in Database. Creates a custom MySQL table with the columns you define in the designer.

Node reference

Overview

Custom Table is a Step (action) in Database. Creates a custom MySQL table with the columns you define in the designer.

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

Custom Table 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 Custom Table to a flow:

  • Custom Table on your linked Joomla site when the flow reaches this step
  • Create table based on webhook, schedule, or CMS event data
  • Integrate Database operations with messaging, AI, or database steps in one canvas

When it runs

Only if the table does not already exist — safe to re-run without dropping data.

Example workflows

Common patterns on the canvas:

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

How to set it up

Table name uses the #__ prefix; column types and keys are set on the Design tab.

Properties panel

The designer shows these tabs for this node:

TabPurpose
InfoPlain-language description and output payload fields for downstream steps
GeneralCanvas label and read-only node ID
AIOptional assistant to help draft settings from plain language
DesignNode-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 keyLabelTypeRequiredVisible whenNotes
_nodeIdNode IDnode-idNo——
_payloadFieldsAvailable Fieldspayload-panelNo——
columnsColumnstable-columnsNo——

User-configured — General tab

Property keyLabelTypeRequiredVisible whenNotes
labelLabeltextNo—Node label

User-configured — Design tab

Property keyLabelTypeRequiredVisible whenNotes
tableNameTable NametextYes—my_custom_table (will be prefixed with #__)

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 {{custom_table.table}}.

Field keyTypeDescription
tablestringTable name alias (same as tableName for custom tables).
tableNamestringDatabase table name used by the node.
tablestringTable name alias (same as tableName for custom tables).
sqlstringSQL query that was executed.

Validation rules

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