# Create Post

<!-- meta: type=wp-create-post; location=Posts; category=Step (action); platforms=Joomla and WordPress (where applicable) -->

## Overview

Create Post 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 **Create Post** 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

Create Post is a **action step** in the **Posts** 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 **Create Post** to a flow:

- Create WordPress post records from webhook or form submissions
- Sync post from a CRM, spreadsheet, or API into WordPress automatically
- Generate post in bulk after a scheduled or Iterator loop

## Example workflows

Common patterns on the canvas:

1. **Webhook** → **Set JSON** → **Create Post** → **Send Email** (confirmation)
2. **Scheduled trigger** → **API REST GET** → **Iterator** → **Create Post**

## 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:

| 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 |
| `title` | Post Title | `payload-text` | **Yes** | — | Title or drag a payload field here |
| `status` | Status | `select` (`draft` \| `publish` \| `pending` \| `private`; default: `draft`) | No | — | — |
| `tagLabels` | Tag names from payload (optional) | `payload-text` | No | — | ["News","Fashion"] or {{node_id.tags}} Optional JSON array of tag **names** after resolving `{{placeholders}}`, e.g. `["News","Fashion"]` or `{{node_id.tags}}`.

Missing WordPress tags are **created** when the flow runs. Values are **merged** with **Tags (existing)** above. Leave both empty on update to keep current tags. |
| `excerpt` | Excerpt (optional) | `textarea` | No | — | Short summary |
| `slug` | Slug (optional) | `payload-text` | No | — | URL slug; auto from title if empty |

### User-configured — Design tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `content` | Content | `wysiwyg` | No | — | Post body |

### CMS-backed or hybrid (loaded from the linked site at design time)

These fields can pull live options or values from the Joomla/WordPress site linked to the flow:

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `author` | Author | `email-recipient` | No | — | User ID, {{placeholder}}, or select user… Value kind: `userId` |

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

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `categoryIds` | Categories | `categories-multi` | No | — | Select one or more categories |
| `tagIds` | Tags (existing) | `tags-multi` | No | — | Select one or more tags |

### 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._

## Validation rules

- **Post Title** (`title`) must be filled before the flow can be saved.

## Related nodes

Other steps in the same area of the palette:

- **Delete Post** (`wp-delete-post`) — Posts
- **Publish Post** (`wp-publish-post`) — Posts
- **Trash Post** (`wp-trash-post`) — Posts
- **Unpublish Post** (`wp-unpublish-post`) — Posts
- **Update Post** (`wp-update-post`) — Posts