Nestr icon

Nestr

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

Actions29

Overview

The node integrates with Nestr, a role-based and self-organized collaboration platform for managing projects, roles, circles, nests, and workspaces. Specifically, the Nest - Get operation retrieves detailed information about a single nest entity within Nestr.

This node is useful when you want to fetch metadata or details about a specific nest in your collaboration environment, such as its properties, relationships, or status. For example, you might use it to display nest details in a dashboard, verify nest configurations before updates, or automate workflows based on nest data.

Properties

Name Meaning
Workspace Name or ID Select the workspace to work with. You can choose from a list of available workspaces or specify an ID using an expression. This determines the context in which the nest exists.
Additional Fields Optional extra parameters to filter or refine the request. Includes:
• Labels: Comma-separated list of labels (not used in "Get" operation for Nest).
• Parent ID: Parent item ID (not used in "Get" operation for Nest).

Note: For the Nest - Get operation, only the workspace selection is relevant; additional fields are not utilized.

Output

The output is a JSON object representing the nest's details as returned by the Nestr API. This typically includes all properties of the nest such as its ID, title, description, associated workspace, labels, ancestors (parent items), and other metadata.

The node outputs this data as a JSON array with one element per input item, each containing the nest information under the json property.

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the Nestr API via OAuth2 authentication.
  • The node depends on the nestrOAuth2Api credential configured in n8n to authenticate requests.
  • The workspace must exist and be accessible with the provided credentials.

Troubleshooting

  • Common issues:

    • Invalid workspace ID: If the workspace ID does not exist or is inaccessible, the API will return an error.
    • Nest not found: Providing an incorrect nest ID (if applicable) will result in a "not found" error.
    • Authentication errors: Missing or expired OAuth2 tokens will cause authorization failures.

  • Error messages and resolutions:

    • "404 Not Found": Verify that the nest and workspace IDs are correct and that the user has access rights.
    • "401 Unauthorized" or "403 Forbidden": Check that the OAuth2 credentials are valid and have sufficient permissions.
    • Network or timeout errors: Ensure stable internet connectivity and that the Nestr API endpoint is reachable.

  • To handle errors gracefully, enable the "Continue On Fail" option in the node settings to allow workflow execution to proceed despite individual item failures.

Links and References

Discussion