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 "Delete Space" operation in the Confluence Cloud node allows users to permanently delete a Confluence space by specifying its unique space key. This deletion bypasses the trash and initiates a long-running task to remove the space, meaning the space might not be immediately deleted when the request returns. Users are advised to poll the returned status link until the deletion completes.
This operation is useful for administrators who want to clean up or remove obsolete spaces from their Confluence instance programmatically. For example, automating the removal of project spaces after project completion or deleting test spaces created during development.
Properties
| Name | Meaning |
|---|---|
| Space Key | The unique key identifier of the space to delete. This is required to specify which space should be removed. |
Output
The output JSON will typically contain information about the initiated deletion task, including a status link that can be polled to check if the space has been fully deleted. Since the deletion is asynchronous, the immediate response does not confirm completion but provides a way to track progress.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token with sufficient permissions.
- The user must have 'Admin' permission for the space to perform deletion.
- The node requires configuration with valid Confluence Cloud credentials and the domain URL of the Confluence instance.
Troubleshooting
Common Issues:
- Attempting to delete a space without admin permissions will result in authorization errors.
- Providing an incorrect or non-existent space key will cause the API to return a not found error.
- Since deletion is asynchronous, assuming immediate deletion may lead to confusion; users should implement polling on the status link.
Error Messages:
- 403 Forbidden: Insufficient permissions to delete the space. Solution: Ensure the API token belongs to a user with admin rights on the target space.
- 404 Not Found: The specified space key does not exist. Solution: Verify the space key is correct.
- 400 Bad Request: Malformed request parameters. Solution: Check that the space key is provided and correctly formatted.