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 Inline Comments" operation of the Comment resource in this Confluence Cloud node retrieves all inline comments across Confluence content. Inline comments are comments tied to specific text selections within pages or blog posts, providing contextual feedback or discussion directly on content fragments.
This operation is useful when you want to programmatically access all inline comments for review, auditing, or integration with other tools such as issue trackers or notification systems. For example, a team lead might use this node to gather all unresolved inline comments from documentation pages to track pending edits or clarifications.
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's response. If available, the representation will be under the same name. |
| - Sort | Field by which to sort the results. |
Note: The operation does not require any mandatory ID or similar input; it fetches all inline comments accessible to the user.
Output
The output JSON contains a list of inline comments with their details. Each comment includes fields such as:
- Comment content (in specified body format if requested)
- Metadata about the comment (author, creation date, status)
- Contextual information linking the comment to the page or blog post and the exact text selection it refers to
- Possible nested replies (children inline comments)
The node returns paginated results limited by the API, with additional results accessible via pagination links if supported.
No binary data output is involved in this operation.
Dependencies
- Requires an authenticated connection to Confluence Cloud via an API key credential.
- The node uses the Confluence Cloud REST API endpoint
/wiki/api/v2/inline-comments. - Proper permissions are required: the user must have permission to view the content of the pages or blog posts where the inline comments exist.
Troubleshooting
- Permission Errors: If the node returns errors related to permissions, ensure that the API key used has sufficient rights to view the content and comments in Confluence.
- Empty Results: If no comments are returned, verify that inline comments exist and that the user has access to them.
- Invalid Body Format: Specifying an unsupported body format may cause errors or empty body fields. Use valid formats supported by Confluence.
- API Rate Limits: Large numbers of comments may hit API rate limits; consider using pagination or limiting the number of results.
Links and References
- Confluence Cloud REST API Documentation - Inline Comments
- Confluence Query Language (CQL) Overview (for advanced filtering in other operations)