Actions35
- Space Actions
- Page Actions
- Template Actions
- Search Actions
- Comment Actions
- Get Page Footer Comments
- Get Page Inline Comments
- Get Blog Post Footer Comments
- Get Blog Post Inline Comments
- Get Custom Content Comments
- Get Footer Comments
- Create Footer Comment
- Get Footer Comment By Id
- Update Footer Comment
- Delete Footer Comment
- Get Footer Comment Children
- Get Inline Comments
- Create Inline Comment
- Get Inline Comment By Id
- Update Inline Comment
- Delete Inline Comment
- Get Inline Comment Children
Overview
This node operation retrieves the root footer comments of a specific blog post from Confluence Cloud. It is useful when you want to fetch all top-level comments that appear at the bottom (footer) of a blog post in Confluence. This can help in scenarios such as aggregating user feedback, monitoring discussions on blog posts, or integrating comment data into other workflows or reporting tools.
For example, you might use this node to:
- Collect all footer comments for a blog post to analyze user engagement.
- Display blog post comments in an external dashboard.
- Trigger notifications or further processing based on new comments added to a blog post.
Properties
| Name | Meaning |
|---|---|
| Id | The ID of the blog post for which footer comments should be returned. |
| Additional Fields | A collection of optional fields to refine the request: |
| - Body Format | The content format type to be returned in the body field of each comment. |
| - Status | Filter comments by their status. Possible values: Current, Deleted, Trashed, Historical, Draft. |
| - Sort | Field name used to sort the results. |
Output
The output will be a JSON array of footer comments related to the specified blog post. Each comment object typically includes details such as the comment's body content (in the requested format), author information, creation date, status, and possibly metadata about replies or likes if available.
If the API supports pagination, the node respects limits and may provide links or tokens to fetch additional pages of comments.
No binary data output is expected from this operation.
Dependencies
- Requires access to a Confluence Cloud instance with appropriate permissions.
- An API authentication credential (such as an API key or token) configured in n8n to authenticate requests to the Confluence Cloud REST API.
- The node uses the Confluence Cloud REST API endpoint
/wiki/api/v2/blogposts/{id}/footer-comments.
Troubleshooting
- Permission Errors: If the node returns permission-related errors, ensure the API credential has permission to view the blog post and its space.
- Invalid Blog Post ID: Providing an incorrect or non-existent blog post ID will result in errors or empty results.
- Empty Results: If no comments are returned, verify that the blog post actually has footer comments and that any filters (status, body format) are not excluding all comments.
- Rate Limits: The Confluence API may enforce rate limits; if exceeded, wait and retry later.
- Malformed Additional Fields: Ensure that optional fields like status and body-format are correctly formatted according to the allowed options.
Links and References
- Confluence Cloud REST API Documentation
- Confluence Permissions Overview
- Confluence Query Language (CQL) (for advanced filtering in other operations)