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
This node interacts with the Plane API to manage "Issue States" within a specified project. The "Get Many" operation retrieves all issue states associated with a given project ID. This is useful for workflows that need to list or process the different states an issue can have in a project management context, such as backlog, in progress, or done.
Practical examples:
- Automating reporting by fetching all issue states to categorize issues.
- Syncing issue states from Plane into another system.
- Triggering actions based on available issue states in a project.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project to fetch issue states from |
Output
The output is a JSON array where each element represents an issue state object retrieved from the Plane API for the specified project. Each issue state typically includes properties like its unique ID, name, group (category), and possibly other metadata defined by the Plane API.
No binary data is involved in this operation.
Dependencies
- Requires an active Plane API credential configured in n8n to authenticate requests.
- The node uses the Plane API endpoints to fetch issue states:
GET /projects/{projectId}/states. - No additional environment variables are required beyond the API authentication.
Troubleshooting
Common issues:
- Invalid or missing Project ID will cause the API request to fail.
- Authentication errors if the Plane API credential is not set up correctly.
- Network or API downtime may result in request failures.
Error messages:
- Errors related to missing parameters will indicate the need to provide a valid Project ID.
- API errors might return HTTP status codes indicating unauthorized access or resource not found.
Resolution tips:
- Ensure the Project ID is correct and corresponds to an existing project in Plane.
- Verify that the Plane API credential is properly configured and has necessary permissions.
- Check network connectivity and Plane API service status.
Links and References
- Plane API Documentation (general reference for endpoints)
- n8n documentation on Using API Credentials