Node reference

Delete Tag for WordPress

Delete Tag performs a WordPress CMS action on your linked site when the flow runs.

Node reference

Overview

Delete Tag performs a WordPress CMS action on your linked site when the flow runs.

Configure fields on the General and Design tabs. Execution is handled by the JOrchestrator WordPress plugin.

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

  • Remove or trash WordPress tag when an external system retires them
  • Clean up tag after a failed validation or approval branch
  • Automate GDPR or retention policies on tag

Example workflows

Common patterns on the canvas:

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

Good to know

Link the flow to a WordPress domain in Domain Setup before testing.

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——

User-configured — General tab

Property keyLabelTypeRequiredVisible whenNotes
labelLabeltextNo—Node label
valueValuetextNo—Enter value

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

_This node does not define standard output payload fields in the designer Info tab._