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 "Issue" resource of the Plane API, specifically supporting the "Get" operation to retrieve details of a single issue within a specified project. It allows users to fetch comprehensive information about an issue by providing the project and issue identifiers.
Common scenarios where this node is beneficial include:
- Retrieving detailed information about a specific issue for reporting or analysis.
- Integrating issue data into workflows that require up-to-date issue status or metadata.
- Automating issue tracking processes by fetching issue details dynamically.
Practical example:
- A user wants to get the current status, description, and assignees of a particular issue in a project to send notifications or update dashboards automatically.
Properties
| Name | Meaning |
|---|---|
| Project Name or ID | The identifier of the project containing the issue. Users can select from a list of projects or specify an ID via expression. If not provided, AI assistance may help match a suitable project based on the description (for other operations). |
| Issue Name or ID | The identifier of the issue to retrieve. Users can select from a list of issues filtered by the selected project or specify an ID via expression. This property is required for the "Get" operation. |
Output
The output JSON contains the full details of the requested issue as returned by the Plane API. This typically includes fields such as:
- Issue ID
- Name/title
- Description
- State/status
- Priority
- Assignees
- Labels
- Other metadata related to the issue
No binary data output is involved in the "Get" operation for issues.
Dependencies
- Requires an active Plane API credential configured in n8n to authenticate requests.
- Depends on the Plane API service being accessible.
- Uses internal helper functions to make HTTP requests to the Plane API endpoints.
Troubleshooting
- Missing or invalid Project ID: Ensure the project ID is correctly specified or selected; otherwise, the API call will fail.
- Invalid Issue ID: The issue ID must exist within the specified project; otherwise, the API returns an error.
- API authentication errors: Verify that the Plane API credentials are valid and have sufficient permissions.
- Network or connectivity issues: Confirm that the Plane API endpoint is reachable from the n8n environment.
- Error messages typically come from the Plane API and indicate issues like "Not Found" for invalid IDs or "Unauthorized" for credential problems.
Links and References
- Plane API Documentation (general reference for API endpoints)
- n8n Expressions Documentation (for using expressions in property values)