Post → Get Many
AI-generatedOverview
This node interacts with the Ghost CMS API (version 2) to manage blog posts, specifically supporting operations on the "Post" resource. It allows users to retrieve multiple posts ("Get Many") from either the Content API or the Admin API source. This is useful for scenarios such as:
- Fetching a list of published blog posts to display in an external application or website.
- Synchronizing posts from Ghost CMS into another system.
- Retrieving posts with specific fields or including related data like authors and tags.
For example, you could use this node to get all posts with their authors and tags included, or limit the number of posts retrieved for performance reasons.
Properties
| Name | Meaning |
|---|---|
| Source | Choose the API source to fetch data from: Admin API or Content API. |
| Return All | Boolean flag indicating whether to return all results or limit the number of posts returned. |
| Limit | Maximum number of posts to return when "Return All" is false. Minimum value is 1. |
| Options | Additional options to customize the request: |
| - Include | Select related entities to include with each post: Authors, Tags. |
| - Fields | Comma-separated string specifying which fields to return for each post. |
| - Formats | Specify content formats to return: |
| - For Content API: HTML, Plaintext | |
| - For Admin API: HTML, Mobile Doc |
Output
The node outputs an array of post objects in the json field. Each object represents a post retrieved from the Ghost CMS API and includes properties depending on the selected options and API source. Typical fields include post metadata (title, slug, status, published date), content in requested formats (HTML, plaintext, or mobiledoc), and optionally related authors and tags if requested.
No binary data output is produced by this operation.
Dependencies
- Requires connection credentials for Ghost CMS:
- An API key credential for the Admin API if "Admin API" source is selected.
- An API key credential for the Content API if "Content API" source is selected.
- The node uses internal helper functions to handle pagination and API requests.
- Timezone handling is done via a timezone library to correctly format scheduled publish dates (not directly relevant for "Get Many" but part of the overall node).
Troubleshooting
- Empty results: Ensure that the correct source (Content API vs Admin API) is selected and that the posts exist in the targeted environment.
- Limit ignored: If "Return All" is set to true, the "Limit" parameter is ignored because all posts are fetched.
- Invalid fields or formats: Providing unsupported field names or formats may result in incomplete data or errors. Use only supported values listed in the properties.
- API authentication errors: Verify that the API key credentials are valid and have sufficient permissions for the selected source.
- Rate limiting: When fetching all posts, large datasets might hit API rate limits; consider using "Limit" or filtering options.