ActionGhostUpdated September 2026

How do I update a Ghost post?

Short answer: You can update ghost post in Ghost by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Ghost Update Ghost Post action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Update Ghost Post in Ghost — start free All 5 Ghost actions

Update Ghost Post in Ghost — start free

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.

Google Sheets → Ghost

2 Google Sheets triggers

HubSpot → Ghost

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Ghost returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Update Ghost Post support batch operations?

Run Update Ghost Post inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Ghost's rate limits.

More actions