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 "Create Footer Comment" operation in the Confluence Cloud node allows users to create a footer comment on various types of content within Confluence. This includes adding comments at the top level on pages or blog posts, replying to existing comments, commenting on attachments, or commenting on custom content. This operation is useful for automating feedback, discussions, or annotations directly within Confluence content.
Practical scenarios include:
- Automatically adding review comments to a page after a workflow step.
- Posting status updates or notes as footer comments on blog posts.
- Replying to existing comments programmatically to continue discussions.
- Adding comments related to attachments or custom content items.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON-formatted data representing the footer comment to create. It must be valid JSON and can specify fields such as pageId, blogPostId, parentCommentId, or attachment/custom content references depending on where the comment should be added. |
Output
The output of this operation is the JSON response from the Confluence API representing the newly created footer comment. This typically includes details such as the comment's ID, body content, author information, creation timestamp, and any metadata associated with the comment.
If the operation supports binary data (not indicated here), it would relate to attachments or media linked to the comment, but this operation focuses on JSON comment data only.
Dependencies
- Requires an active connection to a Confluence Cloud instance.
- Needs an API authentication credential configured in n8n that grants permission to view the target content and create comments in the corresponding space.
- The base URL for API requests is derived from the user's Confluence domain credential.
- Permissions required: Ability to view the content (page, blog post, etc.) and permission to create comments in the relevant space.
Troubleshooting
- Invalid JSON in Request Body: Since the request body must be valid JSON, malformed JSON will cause errors. Ensure the JSON syntax is correct before execution.
- Permission Errors: If the user lacks permission to view the content or create comments, the API will return authorization errors. Verify that the API key has sufficient rights.
- Missing Required Fields: The request body must specify at least one location identifier such as
pageId,blogPostId, orparentCommentId. Omitting these will result in API errors. - API Endpoint Errors: Network issues or incorrect domain configuration can cause failures. Confirm the domain credential is correctly set and reachable.
- Rate Limits: Excessive comment creation may hit API rate limits; handle such errors by implementing retries or backoff strategies.