Actions66
- Board Actions
- Bookmark Actions
- Blog Actions
- Comment Actions
- Discussion Actions
- Documentation Actions
- Label Actions
- Search Actions
Overview
The node integrates with the Discuss Kit API to manage blog content and other discussion-related resources. Specifically, for the Blog resource with the Publish operation, it publishes an existing blog post by its ID. This is useful in workflows where blog posts are drafted or updated programmatically and then published automatically without manual intervention.
Practical examples include:
- Automatically publishing a blog post after content approval.
- Scheduling blog publication as part of a larger content pipeline.
- Integrating blog publishing into multi-channel marketing automation.
Properties
| Name | Meaning |
|---|---|
| Content ID | The unique identifier (ID) of the blog content to be published. This is required to specify which blog post to publish. |
Output
The output is a JSON object representing the published blog post returned from the Discuss Kit API. It typically includes details such as the blog's ID, title, content, locale, slug, publication status, timestamps, and any other metadata provided by the API after publishing.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Discuss Kit API endpoint.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- Uses internal helper functions to make HTTP requests to the Discuss Kit API.
- No additional external services beyond the Discuss Kit API are required.
Troubleshooting
Common issues:
- Invalid or missing Content ID will cause the API call to fail.
- Lack of proper API credentials or expired tokens will result in authorization errors.
- Attempting to publish a blog post that does not exist or is already published may return errors.
Error messages and resolutions:
"error": "Content ID is required"— Ensure the Content ID property is set correctly."error": "Unauthorized"or"error": "Invalid API key"— Verify API credentials are properly configured in n8n."error": "Blog post not found"— Confirm the Content ID corresponds to an existing blog post.- Network timeouts or connectivity issues — Check network connection and API availability.
Links and References
- Discuss Kit API Documentation (hypothetical link)
- n8n HTTP Request Node Documentation (for understanding API request handling)
- UUID Library (used internally for generating IDs in some operations)