How to get ghost post in Ghost

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 or Slug post_id	string	Required	Post ID or Slug. Example: abc123 or my-first-post

Sample request

{
  "post_id": "e.g. abc123 or my-first-post"
}

Returns

{
  "posts": [
    {
      "id": "abc123",
      "html": "<p>Content</p>",
      "slug": "my-first-post",
      "title": "My First Post",
      "status": "published"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Ghost Post.

What does the Get Ghost Post action do in Ghost?

Returns a post by ID or slug with full content, metadata, author info. The standard lookup before update or for cross-system publishing workflows.

What inputs does Get Ghost Post require?

Required: Post ID or Slug. 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 Get Ghost Post support batch operations?

Yes. Run Get Ghost Post inside a Loop node to process arrays. TinyCommand handles Ghost's rate limits automatically so you don't have to throttle manually.

More actions