Short answer: Drop the "Ghost → Update 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 |
|---|---|---|---|
Post ID post_id | string | Required | Post ID. Example: abc123 |
Title title | string | Optional | Title |
HTML Content html | string | Optional | HTML Content |
Status status | options | Optional | Status. Options: Draft, Published, Scheduled |
Updated At updated_at | string | Required | ISO 8601 timestamp of current version (required by Ghost for conflict detection). Get via Get Post. |
{"post_id": "e.g. abc123","title": "{{trigger.title}}","html": "{{trigger.html}}","status": "{{trigger.status}}","updated_at": "e.g. 2025-01-15T12:00:00.000Z"}
{"posts": [{"id": "abc123","title": "Updated Title","status": "published"}]}
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.