Actions43
- 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
- Label Actions
Overview
This node operation retrieves the root inline comments of a specific blog post from Confluence Cloud. Inline comments are comments attached directly to specific parts of the blog post content, often used for detailed feedback or discussions on particular text segments.
Use cases:
- Extracting all inline comments on a blog post for review or processing.
- Automating workflows that analyze or summarize feedback left on blog posts.
- Integrating Confluence inline comments into other collaboration or reporting tools.
Example:
You have a blog post with ID 12345 and want to fetch all inline comments made on it to display them in an external dashboard or send notifications about new comments.
Properties
| Name | Meaning |
|---|---|
| Id | The numeric ID of the blog post for which inline comments should be returned. This is required to specify the target blog post. |
| Additional Fields | Optional collection of additional query parameters to refine the request: - Body Format: Specify the content format type to be returned in the body field of each comment (e.g., storage, view). - Status: Filter comments by their status. Options: Current, Deleted, Trashed, Historical, Draft. - Resolution Status: Filter comments by resolution state. Options: Resolved, Open, Dangling, Reopened. - Sort: Field name to sort the results by. |
Output
The output JSON contains the list of inline comments retrieved for the specified blog post. Each comment object typically includes:
- Comment metadata such as ID, author, creation date.
- The body of the comment in the requested format.
- Status and resolution status fields.
- Possibly nested replies if supported by the API.
No binary data is output by this operation.
Dependencies
- Requires access to a Confluence Cloud instance with appropriate permissions.
- An API authentication credential (API key or token) configured in n8n to authorize requests.
- The node uses the Confluence Cloud REST API endpoint
/wiki/api/v2/blogposts/{id}/inline-comments.
Troubleshooting
- Permission errors: Ensure the API user has permission to view the blog post and its comments.
- Invalid ID: Verify the blog post ID is correct and exists.
- Empty results: Could mean no inline comments exist for the blog post or filters exclude all comments.
- Rate limits: Confluence Cloud APIs may enforce rate limits; handle retries or reduce request frequency.
- Incorrect body format: If specifying a body format, ensure it is supported by the API.