GHOST n8n INTEGRATION: AUTOMATE GHOST WITH N8N

The Get many posts action bulk-retrieves multiple blog posts from your Ghost site in a single operation. This is your go-to action for content audits, bulk exports, feed generation, and any workflow that needs to process your blog catalog at scale.

Key parameters:

• Credential to connect with: Your Ghost Admin account credential, required for authentication.
• Resource: Set to "Post" to work with blog articles.
• Operation: Set to "Get Many" to fetch multiple posts at once.
• Return All: A toggle switch that determines retrieval scope. When ON, fetches every post in your Ghost site. When OFF, respects the Limit parameter.
• Limit: A numeric field to cap how many posts are returned. Default is typically 50. Only applies when "Return All" is OFF.
• Options: Additional filters and parameters to narrow results by status, tag, author, or other criteria.

Use cases:

• Export all blog posts to a backup system or data warehouse nightly
• Generate an RSS feed or custom sitemap from your published content
• Audit all posts to find articles missing featured images or proper tags
• Build a content performance dashboard by pulling all posts into a spreadsheet

When to use it: Whenever you need to work with your blog content in bulk—exports, audits, migrations, or building custom interfaces that display your content.

The Get a post action retrieves a specific blog post from your Ghost site using its unique identifier. This is essential for workflows that need to work with individual pieces of content—updating records, checking publication status, or feeding post data into other systems.

Key parameters:

• Credential to connect with: Select your Ghost Admin account for API authentication. Required for all operations.
• Resource: Set to "Post" to target blog content.
• Operation: Set to "Get" to retrieve a single post.
• By: Determines how you identify the post. Options include "ID" or "Slug", letting you fetch by either the unique database ID or the URL-friendly slug.
• Identifier: A text field where you provide the specific post ID or slug. Required to specify which post to retrieve.
• Options: Additional parameters for including related data like authors or tags.

Use cases:

• Fetch a post's current content before updating it with new information
• Retrieve post metadata to populate a custom analytics dashboard
• Check if a specific article exists before creating a duplicate
• Pull post data to generate social media snippets automatically

When to use it: When your workflow needs information about one specific post rather than browsing through multiple articles. Ideal for update workflows, verification steps, or targeted data extraction.

The Delete post action permanently removes a blog post from your Ghost site. This is a powerful cleanup tool for automating content lifecycle management, removing outdated promotions, or maintaining a lean, relevant blog catalog.

Key parameters:

• Credential to connect with: Select your Ghost Admin account. Required and must have delete permissions.
• Resource: Set to "Post" to target blog content.
• Operation: Set to "Delete" to remove the specified post.
• Post ID: A text field where you enter the unique identifier of the post to delete. Required—the action needs to know exactly which post to remove. Supports expressions for dynamic input.

Use cases:

• Automatically delete promotional posts after their campaign end date
• Remove draft posts that have been abandoned for more than 90 days
• Clean up test content from staging environments before going live
• Delete posts that fail compliance checks in a content moderation workflow

When to use it: For automated content cleanup and lifecycle management. Use with caution—this action is permanent. Consider implementing a "soft delete" workflow that archives posts before deletion for safety.

The Create post action is your gateway to programmatic content publishing. It allows you to generate new blog posts on your Ghost site directly from your n8n workflow, complete with title, content, and formatting—perfect for automated publishing pipelines.

Key parameters:

• Credential to connect with: Select your Ghost Admin account from the dropdown. This is required to authenticate your request and must have write permissions.
• Resource: Set to "Post" to indicate you're working with blog content.
• Operation: Set to "Create" to generate a new post.
• Title: A text field where you enter your post's headline. This is required—every post needs a title.
• Content Format: Choose between "HTML" or "Mobiledoc" format. HTML is the most common choice for content coming from external sources.
• Content: A text area for your post body. Supports HTML markup when HTML format is selected.
• Additional Fields: Optional parameters to set slug, featured image, publication status, tags, and more.

Use cases:

• Automatically publish articles when they're marked "Ready" in your Notion content calendar
• Convert Markdown files from GitHub into formatted Ghost posts
• Create draft posts from approved content briefs for editor review
• Syndicate content from another CMS to your Ghost blog

When to use it: Whenever you need to push new content to Ghost from an external source—content management systems, spreadsheets, writing apps, or AI-generated content pipelines.