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
The node interacts with the "Cycle" resource of the Plane API, specifically supporting the "Get" operation. It retrieves detailed information about a specific cycle within a project by using the provided Project ID and Cycle ID. This is useful for workflows that need to fetch cycle metadata or status as part of project management automation.
Practical examples include:
- Fetching cycle details to display in dashboards or reports.
- Using cycle data to trigger subsequent workflow steps based on cycle attributes.
- Integrating cycle information into other tools or notifications.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project containing the cycle. Required to specify the project context. |
| Cycle ID | The unique identifier of the cycle to retrieve. Specifies which cycle's details to fetch. |
Output
The output JSON contains the full details of the requested cycle as returned by the Plane API. This typically includes fields such as the cycle's name, description, start and end dates, status, and any other metadata associated with the cycle.
No binary data output 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 authenticated HTTP requests to the Plane API endpoints.
- No additional external services are required beyond the Plane API itself.
Troubleshooting
Common issues:
- Invalid or missing Project ID or Cycle ID parameters will cause the API request to fail.
- Network connectivity problems or incorrect API credentials can result in authentication errors.
- If the specified cycle does not exist within the project, the API will return a not found error.
Error messages:
- Errors from the Plane API are propagated; typical messages include "Not Found" if the cycle ID is invalid.
- Authentication errors indicate issues with the API key setup.
Resolutions:
- Verify that both Project ID and Cycle ID are correctly set and correspond to existing resources.
- Ensure the API key credential is valid and has sufficient permissions.
- Check network connectivity and Plane API service status.
Links and References
- Plane API Documentation (for detailed API endpoint info)
- n8n documentation on creating custom nodes