Actions63
- Issue Actions
- Comment Actions
- Cycle Actions
- Cycle Issue Actions
- Issue Attachment Actions
- Issue Property Actions
- Issue Property Option Actions
- Issue Property Value Actions
- Issue State Actions
- Label Actions
- Link Actions
- Member Actions
- Module Actions
- Module Issue Actions
- Project Actions
Overview
This node interacts with the "Cycle" resource of the Plane API, specifically supporting the "Delete" operation among others. The Delete operation removes a specified cycle from a project. This is useful in project management workflows where cycles (iterations or sprints) need to be programmatically cleaned up or removed once they are no longer relevant.
Practical examples include:
- Automatically deleting completed or obsolete cycles as part of a cleanup automation.
- Removing test or placeholder cycles created during development or testing phases.
- Managing project lifecycle by removing cycles that were created in error.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project containing the cycle to delete. |
| Cycle ID | The unique identifier of the cycle to be deleted within the specified project. |
Output
The output JSON contains the response from the Plane API after attempting to delete the specified cycle. Typically, this will be an empty object or confirmation of deletion depending on the API's behavior. No binary data is involved in this operation.
Dependencies
- Requires an active connection to the Plane API via an API key credential configured in n8n.
- The node uses internal helper functions to make HTTP requests to the Plane API endpoints.
- Proper permissions on the Plane API for deleting cycles are necessary.
Troubleshooting
Common issues:
- Invalid or missing Project ID or Cycle ID parameters will cause the API call to fail.
- Insufficient permissions or invalid API credentials can result in authorization errors.
- Attempting to delete a non-existent cycle will likely return a not found error.
Error messages and resolutions:
- "404 Not Found" — Verify that the Project ID and Cycle ID are correct and that the cycle exists.
- "401 Unauthorized" or "403 Forbidden" — Check that the API key credential is valid and has sufficient permissions.
- "400 Bad Request" — Ensure all required parameters are provided and correctly formatted.