Overview
This node triggers an n8n workflow based on events occurring in a Ghost CMS instance. It listens for specific Ghost webhook events such as posts, pages, tags, or members being added, edited, deleted, published, unpublished, scheduled, unscheduled, or rescheduled. When the configured event occurs, the node receives the webhook payload and starts the workflow.
Common scenarios include automating content management tasks, syncing Ghost content with other platforms, or triggering notifications when content changes. For example, you could use this node to automatically share a newly published post on social media or update a search index when a page is edited.
Properties
| Name | Meaning |
|---|---|
| Event | The specific Ghost event that will trigger the workflow. Options include: |
| - Post Added, Post Deleted, Post Edited, Post Published, Post Unpublished, Post Scheduled, Post Unscheduled, Post Rescheduled | |
| - Page Added, Page Deleted, Page Edited, Page Published, Page Unpublished, Page Scheduled, Page Unscheduled, Page Rescheduled | |
| - Tag Added, Tag Edited, Tag Deleted | |
| - Member Added, Member Edited, Member Deleted | |
| Additional Options | Collection of extra settings: |
| Secret | A secret string used to validate that incoming webhook requests genuinely come from Ghost. This helps secure the webhook endpoint by verifying the signature of the request. |
Output
The node outputs the JSON payload received from the Ghost webhook under the json field. This payload contains detailed information about the event, such as the affected post, page, tag, or member data depending on the event type.
No binary data output is produced by this node.
Dependencies
- Requires a valid API key credential with administrative access to the Ghost CMS to create and delete webhooks.
- The node internally manages webhook registration and deletion via Ghost's Admin API.
- The user must configure the "Secret" option to match the secret used in Ghost webhook settings for signature verification.
- No additional environment variables are required beyond standard n8n credentials setup.
Troubleshooting
- Webhook not triggering: Ensure the Ghost webhook is properly created and active. The node attempts to create the webhook automatically but may fail if credentials are invalid or permissions are insufficient.
- Signature validation failed: If the "Secret" property is set, incoming webhook requests must include a matching signature header. Mismatched secrets or missing headers will cause the node to ignore the webhook payload.
- Permission errors: Verify that the API key used has admin rights to manage webhooks in Ghost.
- Empty workflow data: If the webhook payload is empty, check that the correct event is selected and that Ghost is sending the expected data.
Links and References
- Ghost Webhooks Documentation
- Ghost Admin API
- n8n Webhook Node Documentation (for general webhook usage)