List Ghost Posts: Ghost action

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
Limit limit	number	Optional	Limit
Filter filter	string	Optional	Ghost NQL filter

Sample request

{
  "limit": "{{trigger.limit}}",
  "filter": "tag:getting-started"
}

Returns

{
  "posts": [
    {
      "id": "post123",
      "slug": "welcome",
      "title": "Welcome to Ghost",
      "excerpt": "Getting started...",
      "published_at": "2026-04-11T10:00:00Z",
      "feature_image": "https://..."
    }
  ]
}

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

FAQ

Questions about List Ghost Posts.

What does the List Ghost Posts action do in Ghost?

Paginated posts with filters by status, tag, author, date range. For "all posts this month" digest workflows or for syncing to external storage/analytics.

What inputs does List Ghost Posts require?

List Ghost Posts has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Ghost Posts support batch operations?

Yes. Run List Ghost Posts 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