Post → Delete
AI-generatedOverview
This node integrates with the Ghost CMS API (version 2) to manage blog posts, images, and media with enhanced features. Specifically for the Post - Delete operation, it allows users to delete a blog post from their Ghost CMS instance using the Admin API.
Common scenarios where this node is beneficial include:
- Automating content management workflows by programmatically deleting outdated or unwanted posts.
- Integrating Ghost CMS post deletion into larger automation pipelines, such as content lifecycle management or cleanup tasks.
- Managing posts in bulk or based on external triggers without manual intervention in the Ghost admin interface.
Example use case:
- A marketing team uses this node in an n8n workflow to automatically remove promotional posts after a campaign ends, ensuring the website content stays current.
Properties
| Name | Meaning |
|---|---|
| Source | Choose the API source: "Admin API" or "Content API". For deleting posts, only "Admin API" is applicable. |
| Post ID | The unique identifier of the post to delete. Required when using the Admin API to delete a post. |
Output
The output JSON for the delete operation returns an array with a single object indicating success:
[
{
"success": true
}
]
This confirms that the post was successfully deleted.
No binary data output is produced by this operation.
Dependencies
- Requires connection credentials for the Ghost CMS Admin API (an API key or token with appropriate permissions).
- The node depends on internal helper functions to make authenticated HTTP requests to the Ghost Admin API endpoints.
- No additional external services are required beyond access to the Ghost CMS instance.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Post ID will likely result in an error from the Ghost API.
- Using the Content API as the source for deleting posts is not supported; the node expects the Admin API for delete operations.
- Missing or incorrect API credentials will cause authentication failures.
Error messages:
- Errors thrown by the node typically come from failed HTTP requests to the Ghost Admin API, e.g., "Not Found" if the post does not exist.
- Validation errors if required parameters like Post ID are missing.
Resolutions:
- Verify the Post ID is correct and corresponds to an existing post.
- Ensure the node is configured to use the Admin API source for delete operations.
- Confirm that valid API credentials with sufficient permissions are provided.