Actions66
- Board Actions
- Bookmark Actions
- Blog Actions
- Comment Actions
- Discussion Actions
- Documentation Actions
- Label Actions
- Search Actions
Overview
This node integrates with the Discuss Kit API to manage blog content and other discussion-related resources. Specifically, for the Blog - Get operation, it retrieves detailed information about a specific blog post by its unique content ID.
Common scenarios where this node is beneficial include:
- Fetching blog post details dynamically within an automation workflow.
- Integrating blog content retrieval into content management or publishing pipelines.
- Using blog data as input for further processing, such as notifications, analytics, or content syndication.
For example, you might use this node to get a blog post's full details by providing its ID, then use that data to update another system or trigger downstream actions.
Properties
| Name | Meaning |
|---|---|
| Content ID | The unique identifier of the blog post to retrieve. This is required to specify which blog content to fetch. |
Output
The output is a JSON object representing the blog post retrieved from the Discuss Kit API. It typically includes fields such as:
id: The blog post's unique identifier.title: The title of the blog post.content: The main content/body of the blog post.locale: Language or locale of the blog post.slug: URL-friendly identifier for the blog post.boardId: Identifier of the board/category the blog belongs to.labels: Array of labels/tags associated with the blog.assignees: Array of users assigned to the blog post.- Other metadata fields like creation date, update date, cover image, etc.
If the node supports binary data output (not applicable here), it would be summarized accordingly, but this operation returns JSON data only.
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.
Troubleshooting
Error: "Content ID is required"
Ensure that the Content ID property is provided and not empty.Error: "Resource not found" or 404 response
Verify that the Content ID corresponds to an existing blog post. The ID must be correct and the blog post should exist in the Discuss Kit instance.Authentication errors
Confirm that the API credentials are correctly set up and have sufficient permissions to read blog content.Network or timeout issues
Check network connectivity to the Discuss Kit API server and ensure the API endpoint is reachable.
Links and References
- Discuss Kit Official Documentation (for API details and usage)
- n8n HTTP Request Node Documentation (for understanding how API calls are made internally)
This summary focuses on the Blog resource with the Get operation as requested.