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
The "Get Footer Comments" operation for the Comment resource in this Confluence Cloud node retrieves all footer comments from a specified container (such as pages, blog posts, or custom content) within Confluence. Footer comments are comments that appear at the bottom of content items.
This operation is useful when you want to programmatically access discussions or feedback left on Confluence content, enabling workflows such as monitoring comments for moderation, aggregating user feedback, or integrating comment data into other systems.
Practical examples:
- Fetching all footer comments on a specific page to analyze user feedback.
- Retrieving footer comments across multiple blog posts for sentiment analysis.
- Automating notifications based on new comments added to content.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional parameters to customize the request: |
- Body Format: The content format type to be returned in the body field of each comment (e.g., storage, view). |
|
| - Sort: Field name to sort the results by (e.g., creation date, author). |
Note: The operation does not require an explicit ID parameter because it fetches all footer comments globally (not limited to a single page or post).
Output
The output JSON contains a list of footer comments retrieved from the Confluence instance. Each comment object typically includes:
- Metadata about the comment (ID, author, creation date, status).
- The comment body in the requested format (if
body-formatis specified). - Additional properties depending on the API response and expansions.
If the node supports pagination, additional results can be fetched using the next URL provided in the response headers.
No binary data is involved in this operation.
Dependencies
- Requires an authenticated connection to Confluence Cloud via an API key credential.
- The node must be configured with the Confluence domain and valid credentials.
- Permissions required: The user must have permission to view the content of the container and its corresponding space to retrieve footer comments.
Troubleshooting
- Permission errors: If the node returns authorization errors, verify that the API key has sufficient permissions to view the content and comments.
- Empty results: Ensure that the container actually has footer comments and that any filters (like status or sort) are correctly set.
- Invalid body format: If specifying
body-format, use supported formats recognized by Confluence; otherwise, the API may ignore or error on the parameter. - API limits: The Confluence API limits the number of results per call; use pagination if expecting many comments.