List Posts: WordPress 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
Status status	options	Optional	Status. Options: Published, Draft, Any
Per Page per_page	number	Optional	Per Page
Search search	string	Optional	Search. e.g. "Search term"

Sample request

{
  "status": "{{trigger.status}}",
  "per_page": "{{trigger.per_page}}",
  "search": "Search term"
}

Returns

[
  {
    "id": 42,
    "date": "2026-04-11T10:00:00",
    "link": "https://your-site.com/my-post/",
    "title": {
      "rendered": "My Post"
    },
    "status": "publish"
  }
]

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

FAQ

Questions about List Posts.

What does the List Posts action do in WordPress?

Lists recent WordPress posts, with filters for status, author, category, and date. Useful for newsletter generators or for syncing content elsewhere.

What inputs does List Posts require?

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

Yes. Run List Posts inside a Loop node to process arrays. Tiny Command handles WordPress's rate limits automatically so you don't have to throttle manually.

More actions