Plane icon

Plane

Consume Plane API
Join our community

Actions63

Overview

The node interacts with the Plane API to manage issues within projects. Specifically, the "Issue - Get Many" operation retrieves multiple issues from a specified project, optionally filtered by criteria such as issue state, priority, or labels.

This operation is useful when you want to:

  • List all issues in a project for reporting or monitoring.
  • Retrieve issues matching certain states (e.g., "in progress", "backlog") or priorities (e.g., "urgent").
  • Filter issues by labels to focus on specific categories or tags.

Practical example:
You might use this node to fetch all high-priority issues labeled "API" in a project, then trigger notifications or generate dashboards based on that data.

Properties

Name Meaning
Project Name or ID The identifier of the project from which to retrieve issues. You can select from a list of available projects or specify an ID via expression. If not provided, AI assistance may help match a suitable project based on description.
Filters A collection of optional filters to narrow down the issues returned:
  State Names or IDs Filter issues by their state(s). Choose one or more states from the list or specify IDs via expression.
  Priority Filter issues by priority level. Options include: High, Low, Medium, None, Urgent.
  Label Names or IDs Filter issues by label(s). Choose one or more labels from the list or specify IDs via expression.

Output

The output is a JSON array where each element represents an issue object retrieved from the Plane API. Each issue object typically contains fields such as:

  • Issue ID
  • Name/title
  • Description
  • State
  • Priority
  • Labels
  • Assignees
  • Other metadata related to the issue

The exact structure depends on the Plane API's response schema for issues.

This operation does not produce binary data.

Dependencies

  • Requires a valid Plane API credential configured in n8n to authenticate requests.
  • Uses the Plane API endpoints to fetch projects, issue states, labels, and issues.
  • For loading options (like project lists, states, labels), it calls Plane API endpoints dynamically.
  • No additional external services are required for the "Get Many" operation itself.

Troubleshooting

  • Common issues:

    • Missing or invalid project ID: Ensure the project ID is correctly specified or selected.
    • No issues returned: Check if the filters are too restrictive or if the project actually contains issues.
    • API authentication errors: Verify that the Plane API credentials are correctly set up and have necessary permissions.

  • Error messages:

    • Errors from the Plane API will be propagated, e.g., "Project not found" or "Unauthorized".
    • If the node fails to load options like projects or labels, check network connectivity and API key validity.
    • When using expressions for IDs, ensure they resolve to valid values.

Links and References

Discussion