Nestr icon

Nestr

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

Actions29

Overview

This node interacts with the "Role" resource in the Nestr project management and collaboration platform, specifically to retrieve multiple roles ("Get Many" operation). It allows users to fetch a list of roles associated with a specific workspace, optionally filtered by labels or parent role ID. This is useful for managing and organizing roles within a workspace, such as when automating user permissions, auditing roles, or integrating role data into other workflows.

Practical examples include:

  • Retrieving all roles in a workspace to display them in a dashboard.
  • Filtering roles by labels to find specific categories of roles.
  • Fetching roles under a certain parent role to understand role hierarchies.

Properties

Name Meaning
Workspace Name or ID Select the workspace to work with. Choose from a list of available workspaces or specify an ID using an expression.
Additional Fields Optional filters to narrow down results:
- Labels Comma-separated list of labels to filter roles by.
- Parent ID Filter roles that have the specified parent role ID.
Return All Whether to return all matching roles or limit the number of results returned.
Limit Maximum number of roles to return if not returning all (minimum 1).

Output

The output is a JSON array where each item represents a role object retrieved from the Nestr API. Each role object contains details about the role such as its ID, title, labels, parent relationships, and other metadata as provided by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Nestr API via an OAuth2 API credential.
  • The node depends on the Nestr API endpoints for workspaces and roles.
  • The workspace must exist and be accessible with the provided credentials.
  • The node uses internal helper methods to paginate and fetch all items if requested.

Troubleshooting

  • Common issues:

    • Invalid or missing workspace ID: Ensure the workspace exists and the ID is correct.
    • Insufficient permissions: The API key or OAuth token must have access rights to read roles in the workspace.
    • Network or API errors: Check connectivity and Nestr service status.

  • Error messages:

    • Errors returned from the API will be surfaced, e.g., "Workspace not found" or "Unauthorized".
    • If "Return All" is false and the limit is set too low, you may get fewer results than expected.

  • Resolutions:

    • Verify workspace selection and credentials.
    • Increase the limit or enable "Return All" to fetch more roles.
    • Handle errors gracefully by enabling "Continue On Fail" in the node settings if partial data is acceptable.

Links and References

Discussion