Confluence Cloud icon

Confluence Cloud

Access to the Confluence Cloud REST API - Auto-generated from OpenAPI

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.
  • Automate moderation workflows by fetching and processing comments.

Properties

Name Meaning
Id The ID of the blog post for which footer comments should be returned.
Additional Fields Optional parameters 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 associated with the specified blog post. Each comment object typically includes details such as the comment body (in the requested format), author information, creation date, status, and possibly metadata like likes or versioning if supported.

If the body-format option is specified, the comment's body content will be returned in that format, potentially including multiple representations under the body field.

No binary data output is expected from this operation.

Dependencies

  • Requires access to a Confluence Cloud instance with appropriate permissions.
  • An API authentication token or API key credential 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 errors, ensure the API credentials have 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 no comments or an error. Verify the blog post ID before running.
  • Empty Results: If no comments are returned, check if the blog post actually has footer comments and that filters (status, etc.) are not excluding all results.
  • API Rate Limits: Be aware of Confluence API rate limits; excessive calls may be throttled.
  • Incorrect Body Format: Specifying an unsupported body-format may cause the API to ignore the parameter or return unexpected formats.

Links and References

Discussion