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 collaboration platform to manage "Circles" within a specified workspace. The Get Many operation retrieves multiple circles from a selected workspace, optionally filtered by labels or parent circle ID. This is useful for scenarios where you want to list or process groups of circles in a workspace, such as displaying all circles for reporting, automation, or synchronization with other tools.

Practical examples:

  • Fetching all circles in a workspace to display them in a dashboard.
  • Retrieving circles filtered by specific labels to automate notifications or assignments.
  • Getting child circles under a parent circle to analyze hierarchical structures.

Properties

Name Meaning
Workspace Name or ID Select the workspace to work with. Choose from a dropdown list or specify an ID via expression.
Additional Fields Optional filters:
- Labels Comma-separated list of labels to filter circles by.
- Parent ID Filter circles that have this parent circle ID.
Return All Whether to return all matching results or limit the number returned (only shown for getAll).
Limit Maximum number of results to return if not returning all (minimum 1, default 50).

Output

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

No binary data is output by this node.

Dependencies

  • Requires an active connection to the Nestr API using OAuth2 authentication.
  • The node depends on the nestrApiRequest helper function to make authenticated HTTP requests to the Nestr REST API.
  • The user must configure the node with valid credentials that allow access to the target workspace.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication errors.
    • Specifying a non-existent workspace ID will result in a "not found" error.
    • Using invalid label filters or parent IDs may return empty results.
    • Network connectivity problems can cause request timeouts or failures.

  • Error messages and resolutions:

    • "401 Unauthorized": Check and refresh your API credentials.
    • "404 Not Found": Verify the workspace ID and ensure it exists.
    • "400 Bad Request": Confirm that label filters and parent IDs are correctly formatted.
    • "Request failed" or timeout errors: Ensure stable internet connection and API availability.

Links and References

Discussion