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 Plane API to manage issues associated with project cycles. Specifically, for the "Cycle Issue" resource and the "Get Issues" operation, it retrieves all issues linked to a specified cycle within a given project.
This node is useful in scenarios where you want to automate or integrate workflows involving issue tracking within project cycles. For example, you might use it to:
- Fetch all issues assigned to a particular development cycle to generate reports.
- Synchronize cycle issues with other project management tools.
- Trigger downstream automation based on the current set of issues in a cycle.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project containing the cycle. This is required to specify the project context. |
| Cycle ID | The unique identifier of the cycle whose issues you want to retrieve. This is required to specify the target cycle. |
Output
The output is an array of JSON objects representing the issues associated with the specified cycle. Each object contains detailed information about an individual issue as returned by the Plane API's /projects/{projectId}/cycles/{cycleId}/cycle-issues endpoint.
The exact structure of each issue object depends on the Plane API but typically includes fields such as issue ID, name, description, status, assignees, labels, priority, and other metadata relevant to the issue.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Plane API via an authenticated API key credential configured in n8n.
- The node uses internal helper functions to make HTTP requests to the Plane API endpoints.
- Proper configuration of the Plane API credentials in n8n is necessary for successful execution.
Troubleshooting
- Missing or invalid Project ID or Cycle ID: Ensure that both IDs are correctly provided and correspond to existing entities in your Plane workspace.
- Authentication errors: Verify that the Plane API credential is correctly set up and has sufficient permissions.
- Empty results: If no issues are returned, confirm that the specified cycle actually contains issues.
- API rate limits or network issues: These can cause request failures; check network connectivity and Plane API usage limits.
- Error messages from the Plane API: The node will throw errors if the API returns error responses; review the error message details for guidance.
Links and References
- Plane API Documentation (general reference for endpoints and data structures)
- n8n documentation on creating custom nodes