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 property options within a project management context. Specifically, for the "Issue Property Option" resource and the "Get" operation, it retrieves details of a specific option associated with an issue property in a given project.
Common scenarios where this node is beneficial include:
- Fetching metadata about configurable options for custom properties on issues.
- Integrating Plane's issue property options into automated workflows for reporting or synchronization.
- Validating or displaying available options for issue properties before updating or creating issues.
For example, if you have a custom dropdown property on issues representing priority levels, this node can retrieve the details of a particular priority option by its ID.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project containing the issue property option. |
| Property ID | The unique identifier of the issue property to which the option belongs. |
| Option ID | The unique identifier of the specific issue property option to retrieve. |
Output
The output JSON contains the detailed information of the requested issue property option as returned by the Plane API. This typically includes fields such as the option's name, ID, and any other metadata defined by Plane for issue property options.
No binary data output is involved in this operation.
Dependencies
- Requires an active Plane API credential configured in n8n to authenticate requests.
- Depends on the Plane API being accessible and the provided IDs (project, property, option) being valid.
- Uses internal helper functions to make HTTP GET requests to Plane API endpoints.
Troubleshooting
- Invalid or missing IDs: Ensure that the Project ID, Property ID, and Option ID are correctly specified and correspond to existing entities in Plane.
- Authentication errors: Verify that the Plane API credential is properly set up and has sufficient permissions.
- Network or API errors: Check network connectivity and Plane API status.
- Error messages: If the node throws errors related to fetching data, confirm that the resource and operation parameters are correct and that the Plane API endpoint paths have not changed.
Links and References
- Plane API Documentation (general reference for API endpoints)
- n8n documentation on creating custom nodes