List Tags
ghost.content_list_tags
ActionBusiness appsconnection required
Calls the Ghost API with the connection's credentials.
List the site's public tags through the Content API, ordered by name. Use it to resolve a tag slug before filtering posts by it.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Ghost
- Secret shape
- {"admin_api_key": "<id>:<secret>", "content_api_key": "…"}
- Config it needs
- admin_url, api_version
- Resolved by
- config.connection_id, else node.connection_id
Configuration
6 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
filter An NQL filter to narrow the results, such as 'status:draft' or 'tag:getting-started+featured:true'. | string | No | — | — | — |
order Sort order in SQL style, such as 'published_at desc' or 'title asc'. | string | No | — | — | — |
limit How many records to return in one page. Ghost returns 15 by default and caps a page at 100. | number | No | — | 1–100 | — |
page Which 1-based page of the result set to return. | number | No | — | ≥ 1 | — |
include Extra related data to load. 'count.posts' adds how many published posts use each record. | string | No | — | one of "count.posts" | — |
fields Comma-separated list of fields to return, for a leaner response (for example 'id,title,url'). Does not combine well with include. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The tags on this page of results. | array | — |
count How many tags are in items. | number | — |
pagination.total How many tags match the query in total. | number | — |
{
"count": 0,
"items": [],
"pagination": {
"total": 0
}
}Notes
- GET /ghost/api/content/tags/?key=…
- Content API: published records only, and never a draft. It uses the connection's content_api_key, not the Admin API key.
See List Tags run in a workflow.
In a technical demo we add the Ghost connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.