Short answer: Drop the "WordPress → Create Post" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Title title | string | Required | Title. e.g. "My New Post" |
Content content | html | Required | Content. e.g. "<p>Post content here...</p>" |
Status status | options | Optional | Status. Options: Draft, Published, Private, Pending Review |
Excerpt excerpt | string | Optional | Excerpt |
Category IDs categories | string | Optional | Comma-separated category IDs |
Tag IDs tags | string | Optional | Comma-separated tag IDs |
{"title": "My New Post","content": "<p>Post content here...</p>","status": "{{trigger.status}}","excerpt": "{{trigger.excerpt}}","categories": "1,5,12"}
{"id": 42,"date": "2026-04-11T10:00:00","link": "https://your-site.com/?p=42","title": {"rendered": "My New Post"},"status": "draft"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.