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 "Update Inline Comment" operation in the Confluence Cloud node allows users to update an existing inline comment on a Confluence page or blog post. This includes modifying the body text of the comment and optionally resolving the comment. Inline comments are typically used to annotate specific parts of content, such as highlighted text within a page.
This operation is beneficial when you want to programmatically edit or resolve inline comments without manually accessing the Confluence UI. For example, you might automate workflows that update comments based on external review feedback or mark comments as resolved after addressing them.
Properties
| Name | Meaning |
|---|---|
| Comment Id | The unique numeric ID of the inline comment to be updated. |
| Request Body | JSON object containing the data to update the inline comment. Typically includes fields like the updated comment body text and resolution status. |
Output
The output of this operation is the JSON response from the Confluence Cloud API representing the updated inline comment. This JSON will include details such as the comment's ID, updated body content, status (e.g., resolved or open), author information, timestamps, and any other metadata provided by the API.
No binary data is involved in this operation.
Dependencies
- Requires an active connection to Confluence Cloud via an API key credential configured in n8n.
- The node uses the Confluence Cloud REST API endpoint for inline comments.
- Proper permissions are required: the user must have permission to view the content and create/update comments in the relevant space.
Troubleshooting
- Invalid Comment Id: If the specified comment ID does not exist or is incorrect, the API will return an error indicating the comment was not found. Verify the comment ID before updating.
- Permission Denied: Errors related to insufficient permissions may occur if the API token lacks rights to update comments or view the content. Ensure the API key has appropriate scopes and the user has necessary Confluence permissions.
- Malformed JSON in Request Body: The request body must be valid JSON. Invalid JSON syntax will cause the request to fail. Use proper JSON formatting.
- API Rate Limits: Frequent updates may hit Confluence API rate limits. Implement retry logic or reduce request frequency if encountering rate limit errors.