Short answer: Drop the "Ghost → Create Ghost 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. Example: Getting Started with Our API |
HTML Content html | string | Required | HTML Content. e.g. "<p>Welcome to our blog...</p>" |
Status status | options | Optional | Status. Options: Draft, Published, Scheduled |
Tags tags | string | Optional | Comma-separated tag names (created automatically if they don't exist) |
Custom Excerpt excerpt | string | Optional | Short description shown in post previews |
Featured featured | options | Optional | Featured. Options: No, Yes |
{"title": "e.g. Getting Started with Our API","html": "<p>Welcome to our blog...</p>","status": "{{trigger.status}}","tags": "e.g. tutorial, api","excerpt": "{{trigger.excerpt}}"}
{"posts": [{"id": "abc123","url": "https://yourblog.com/getting-started/","slug": "getting-started","title": "Getting Started","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.