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 integrates with the Plane API to manage issues within projects. Specifically, the "Issue - Create" operation allows users to create a new issue in a specified project. It supports setting essential details like the issue's name/title and various optional fields such as description, state, priority, assignees, labels, cycle, and module associations.
Common scenarios where this node is beneficial include:
- Automating issue creation from external triggers or workflows.
- Integrating Plane issue tracking with other tools by programmatically adding issues.
- Quickly logging bugs, tasks, or feature requests into a project management system.
Practical example:
- When a customer support ticket is received via email, automatically create a corresponding issue in Plane with relevant details and assign it to the appropriate team members.
Properties
| Name | Meaning |
|---|---|
| Project Name or ID | The target project where the issue will be created. Choose from a list of available projects or specify an ID using an expression. If not provided, AI assistance can help match a suitable project based on the description. |
| Name | The title or name of the issue. This is a required field. |
| Additional Fields | Optional extra fields to provide more context or metadata for the issue: |
| - Description HTML | HTML content describing the issue in detail. |
| - State Name or ID | The current state of the issue (e.g., backlog, in progress). Select from available states for the project or specify an ID. |
| - Priority | The urgency level of the issue. Options are: High, Low, Medium, None, Urgent. |
| - Assignee Names or IDs | Users to assign the issue to. Multiple assignees can be selected from the project members or specified by IDs. |
| - Label Names or IDs | Labels/tags to associate with the issue for categorization. Multiple labels can be selected or specified by IDs. |
| - Cycle Name or ID | The development cycle or sprint to associate the issue with. Choose from existing cycles or specify an ID. |
| - Module Name or ID | The module or component related to the issue. Select from existing modules or specify an ID. |
Output
The output JSON contains the newly created issue object returned from the Plane API. This includes all standard issue properties such as:
id: Unique identifier of the issue.name: Title of the issue.description_html: Detailed HTML description.priority: Priority level.state: Current state information.assignees: List of assigned user IDs.labels: Associated label IDs.cycle: Associated cycle ID.module: Associated module ID.- Additional metadata including AI analysis if AI-assisted project matching was used.
No binary data output is produced by this operation.
Dependencies
- Requires a valid Plane API credential configured in n8n to authenticate requests.
- Optionally uses an AI service (Deepseek via OpenAI) for automatic project matching and enriched issue description when the project ID is not explicitly provided.
- The node depends on several internal helper methods to fetch options dynamically (projects, members, states, labels, cycles, modules).
Troubleshooting
- Missing or invalid project ID: If no project ID is provided and AI assistance fails to find a suitable project, the node will throw an error indicating it cannot determine the appropriate project. Provide a valid project ID or ensure the AI key is correctly set.
- Invalid assignee or label IDs: Ensure that assignees and labels exist in the specified project; otherwise, the API may reject the request.
- API authentication errors: Verify that the Plane API credentials are correctly configured and have sufficient permissions.
- Error parsing AI response: If AI-based enrichment is enabled but the response lacks required fields (like state), the node will throw an error. Check the AI API key and network connectivity.
- Binary data errors: Not applicable for this operation since it does not handle binary data.
Links and References
- Plane API Documentation
- n8n Expressions Documentation
- Deepseek AI Service (used optionally for AI-assisted project matching and issue enrichment)