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 operation creates a new issue state within a specified project in the Plane API. Issue states represent different stages or statuses that an issue can have during its lifecycle, such as "Backlog," "Started," or "Completed." Creating custom issue states allows teams to tailor their workflow and track issues more precisely according to their processes.
Common scenarios:
- Defining new workflow stages for issues in a project.
- Adding a custom status to better reflect the team's process (e.g., "Cancelled" or "Unstarted").
- Setting up default states for new issues to streamline issue creation.
Practical example:
A project manager wants to add a new issue state called "In Review" under the "Started" group to indicate that an issue is currently being reviewed by peers. Using this node, they specify the project ID, name the state "In Review," assign it to the "Started" group, optionally set a color and description, and create the state via the Plane API.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project where the issue state will be created. |
| Name | The name of the new issue state (e.g., "In Review"). |
| Group | The category/group this state belongs to. Options: Backlog, Cancelled, Completed, Started, Unstarted. |
| Additional Fields | Optional extra settings for the issue state: |
| - Color | A hex color code representing the state's color (e.g., "#2563eb"). |
| - Description | A textual description explaining the purpose or details of the state. |
| - Default | Boolean flag indicating if this state should be the default for new issues in the project. |
Output
The output JSON contains the newly created issue state object returned from the Plane API. This typically includes:
id: Unique identifier of the created state.name: Name of the state.group: Group/category the state belongs to.color: Color code assigned to the state.description: Description text of the state.default: Whether this state is the default for new issues.- Other metadata fields as provided by the Plane API.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Plane API with appropriate authentication credentials (an API key or token).
- The node depends on the Plane API endpoint
/projects/{projectId}/states/for creating issue states. - Proper configuration of the Plane API credential in n8n is necessary.
Troubleshooting
- Missing or invalid Project ID: Ensure the
Project IDproperty is correctly set and corresponds to an existing project in Plane. - Invalid group value: The
Groupmust be one of the predefined options; using an unsupported value will cause errors. - API authentication errors: Verify that the Plane API credentials are valid and have permissions to create issue states.
- Color format issues: The color field expects a valid hex color code; incorrect formats may be rejected.
- Default state conflicts: If setting multiple states as default, the API might reject the request or override previous defaults.
If the node throws errors related to HTTP requests, check network connectivity and API rate limits.