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 allows you to create a footer comment in Confluence Cloud. Footer comments are comments that appear at the bottom of pages, blog posts, attachments, or custom content within Confluence. You can create a new top-level footer comment by specifying the page or blog post ID, reply to an existing comment by specifying a parent comment ID, or associate the comment with an attachment or custom content.
This operation is useful for automating feedback collection, discussions, or annotations on Confluence content programmatically. For example, you might use it to automatically add review comments after a document update or to integrate external systems that generate comments based on events.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON data representing the footer comment to create. This includes fields like pageId, blogPostId, parentCommentId, or content details depending on where the comment should be attached. |
The "Request Body" property expects a JSON object describing the comment details. It must be valid JSON and will be parsed before sending.
Output
The output of this operation is the JSON response from the Confluence Cloud API representing the created footer comment. This typically includes:
- The unique ID of the new comment.
- Metadata about the comment such as creation time, author, and status.
- The body/content of the comment.
- Links and other related properties.
No binary data is involved in this operation.
Dependencies
- Requires access to a Confluence Cloud instance.
- Requires an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API requests is derived from the domain specified in the credentials.
- Permissions: The user must have permission to view the target content (page, blog post, etc.) and permission to create comments in the corresponding space.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" field is malformed, the request will fail. Ensure the JSON syntax is correct.
- Permission Errors: If the user lacks permission to view the content or create comments, the API will return an authorization error. Verify permissions in Confluence.
- Missing Required Fields: The request body must include identifiers such as
pageIdorblogPostIdfor top-level comments, orparentCommentIdfor replies. Omitting these may cause errors. - API Endpoint Errors: Network issues or incorrect domain configuration in credentials can cause failures. Confirm the domain and connectivity.