Nestr icon

Nestr

Manage projects, roles, circles, and workspaces in Nestr - Role-based and self-organized collaboration
Join our community

Actions29

Overview

This node integrates with the Nestr project management platform to manage projects within workspaces. Specifically, the Get Many operation for the Project resource retrieves multiple projects from a specified workspace. It supports fetching either all projects or a limited number of them, optionally filtered by labels or parent project ID.

Typical use cases include:

  • Synchronizing project lists from Nestr into other tools.
  • Automating reporting or dashboards that require bulk project data.
  • Filtering and processing projects based on workspace context and metadata like labels.

For example, you might use this node to fetch all projects in a workspace tagged with certain labels to generate a status report or to trigger workflows based on project hierarchies.

Properties

Name Meaning
Workspace Name or ID Selects the workspace to retrieve projects from. Can be chosen from a list or specified via expression.
Additional Fields Optional filters for the query:
• Labels: Comma-separated list of labels to filter projects.
• Parent ID: Filter projects by their parent item ID.
Return All Boolean flag indicating whether to return all matching projects or limit the number of results.
Limit Maximum number of projects to return if "Return All" is false. Minimum value is 1.

Output

The node outputs an array of JSON objects representing projects retrieved from the specified workspace. Each project object contains fields as defined by the Nestr API, typically including:

  • Project ID
  • Title
  • Description
  • Associated workspace ID
  • Labels (as an array)
  • Ancestors (parent project IDs if any)

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Nestr API using OAuth2 authentication.
  • The node depends on the nestrApiRequest and nestrApiRequestAllItems helper functions to communicate with the Nestr REST API.
  • The user must configure valid credentials with appropriate permissions to access workspace and project data.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication failures.
    • Specifying a non-existent workspace ID will result in errors or empty results.
    • Using incorrect label formats in the "Additional Fields" may lead to no matches.

  • Error messages:

    • Authentication errors usually indicate invalid or missing API tokens; re-authenticate or update credentials.
    • "Not Found" errors suggest the workspace or projects do not exist or are inaccessible; verify IDs and permissions.
    • Rate limiting or network errors may occur; retry after some time or check network connectivity.

Links and References

Discussion