- Integrations
- /
- Ghost
- /
- Actions
- /
- Update Ghost Post
ActionGhostUpdated May 2026
How do I update a Ghost post?
Short answer: Drop the "Ghost → Update Ghost Post" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
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. |
Sample request
{"post_id": "e.g. abc123","title": "{{trigger.title}}","html": "{{trigger.html}}","status": "{{trigger.status}}","updated_at": "e.g. 2025-01-15T12:00:00.000Z"}
Returns
{"posts": [{"id": "abc123","title": "Updated Title","status": "published"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Update Ghost Post.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Update Ghost Post.
What does the Update Ghost Post action do in Ghost?
Updates an existing post. Ghost enforces optimistic concurrency via updated_at — pass the current value from Get Post. For "edit this post to add a banner" or "auto-republish with new SEO meta" workflows.
What inputs does Update Ghost Post require?
Required: Post ID, Updated At. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Ghost returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Update Ghost Post support batch operations?
Yes. Run Update Ghost Post inside a Loop node to process arrays. Tiny Command handles Ghost's rate limits automatically so you don't have to throttle manually.
More actions
Other Ghost actions.
Action
Create Ghost Post
Creates a draft, scheduled, or published post with HTML or mobiledoc body, feature image, tags. For "Git commit pushes markdown → publish to Ghost" or "AI-generated draft → post for review" workflows.
ActionDelete Ghost Post
Permanently removes a post. Irreversible. For cleanup workflows or for "outdated content cleanup" maintenance.
ActionGet Ghost Post
Returns a post by ID or slug with full content, metadata, author info. The standard lookup before update or for cross-system publishing workflows.
ActionList Ghost Posts
Paginated posts with filters by status, tag, author, date range. For "all posts this month" digest workflows or for syncing to external storage/analytics.
Send update ghost post from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.