Actions63
- Comment Actions
- Cycle Actions
- Cycle Issue Actions
- 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 project cycles. Specifically, the "Cycle" resource with the "Get Many" operation retrieves all cycles associated with a specified project. This is useful for workflows that need to list or process multiple development or work cycles within a project management context.
Common scenarios include:
- Fetching all cycles in a project to display or analyze their statuses.
- Automating reports or dashboards that summarize cycle progress.
- Integrating cycle data into other tools or processes for enhanced project tracking.
Example: A user wants to get all cycles of a project to trigger notifications when new cycles are created or to aggregate cycle metrics.
Properties
Name | Meaning |
---|---|
Project ID | The unique identifier of the project whose cycles you want to retrieve. This is required to specify the project context for fetching cycles. |
Output
The output is a JSON array where each element represents a cycle object retrieved from the Plane API for the specified project. Each cycle object typically contains details such as the cycle's ID, name, and any additional metadata provided by the API.
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 GET requests to the Plane API endpoints.
- The "Project ID" must be valid and correspond to an existing project in Plane.
Troubleshooting
- Invalid Project ID: If the provided Project ID does not exist or is incorrect, the API call will fail. Verify the Project ID is correct.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to access project cycles.
- Empty Results: If no cycles are returned, confirm that the project actually has cycles defined.
- API Rate Limits or Downtime: Temporary API issues may cause failures; retry after some time or check Plane API status.
Common error messages:
- Unauthorized or 401 errors indicate invalid or missing API credentials.
- 404 errors suggest the project or resource was not found.
- Network errors may indicate connectivity problems.
Links and References
- Plane API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding API calls
- Plane project and cycle concepts overview (check Plane official docs or support)