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 issues within project modules. Specifically, the "Add Issues to Module" operation allows users to associate multiple existing issues with a particular module inside a project. This is useful for organizing and grouping related issues under specific functional or logical parts of a project.
Common scenarios include:
- Structuring a software development project by linking bug reports or feature requests to relevant modules.
- Managing tasks in large projects by categorizing issues into modules for better tracking.
- Automating issue assignment workflows where issues are dynamically added to modules based on certain triggers.
Example: You have a project with several modules representing different components (e.g., frontend, backend). When new issues are created, you can use this node to add those issues to the appropriate module automatically.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project containing the module and issues. |
| Module ID | The unique identifier of the module to which issues will be added. |
| Issue IDs | A comma-separated list of issue IDs that you want to add to the specified module. |
Output
The output JSON contains the response from the Plane API after adding the specified issues to the module. Typically, it includes details about the updated module-issue associations or confirmation of the successful addition.
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 service being accessible and responsive.
- Uses internal helper functions to make HTTP requests to Plane API endpoints.
Troubleshooting
- Invalid Project or Module ID: If the provided project or module ID does not exist or is incorrect, the API will return an error. Verify the IDs before running the node.
- Malformed Issue IDs: Ensure the issue IDs are correctly formatted as a comma-separated string without extra spaces or invalid characters.
- API Authentication Errors: Check that the Plane API credentials are valid and have sufficient permissions.
- Network Issues: Connectivity problems may cause request failures; verify network access to the Plane API endpoint.
- Error Messages: The node throws errors with messages returned from the Plane API. Review these messages for clues on what went wrong (e.g., permission denied, resource not found).
Links and References
- Plane API Documentation (general reference for API endpoints)
- n8n documentation on Using Credentials
- n8n community forums for troubleshooting and examples