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 Space" operation in the Confluence Cloud node allows users to update properties of an existing Confluence space, such as its name, description, or homepage. This operation is useful for administrators who want to programmatically modify space details without using the Confluence user interface. For example, you might use this node to rename a project space, update its description to reflect new information, or change the homepage content dynamically based on external data.
Properties
| Name | Meaning |
|---|---|
| Space Key | The unique key identifier of the Confluence space that you want to update. |
| Request Body | JSON object containing the data to update in the space, such as name, description, etc. |
Output
The output of this operation is the JSON response from the Confluence API representing the updated space object. It typically includes fields like the space's key, name, description, and other metadata reflecting the current state after the update.
No binary data is output by 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.
- The user must have 'Admin' permission for the target space to perform updates.
Troubleshooting
Common Issues:
- Insufficient permissions: The user must have admin rights on the space; otherwise, the API will reject the update.
- Invalid space key: Providing a non-existent or incorrect space key will result in an error.
- Malformed JSON in the request body: The request body must be valid JSON; otherwise, parsing errors occur.
Error Messages:
- 403 Forbidden: Indicates lack of admin permission on the space. Solution: Verify user permissions.
- 404 Not Found: The specified space key does not exist. Solution: Check the space key value.
- 400 Bad Request: Usually due to invalid JSON or unsupported fields in the request body. Solution: Validate JSON syntax and API documentation for allowed fields.