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 platform to manage roles within workspaces. Specifically, the Role - Update operation allows users to update an existing role's properties such as labels and parent relationships within a specified workspace.

Typical use cases include:

  • Modifying role metadata to reflect organizational changes.
  • Adding or removing labels for categorization or filtering.
  • Changing the hierarchical structure by updating the parent role.

For example, you might update a role to add new labels indicating its responsibilities or assign it under a different parent role to reorganize team structures.

Properties

Name Meaning
Workspace Name or ID Select the workspace where the role exists. Can be chosen from a list or specified by ID.
Additional Fields Optional fields to update on the role:
  Labels Comma-separated list of labels to assign to the role (e.g., "admin, manager").
  Parent ID The ID of the parent role to establish a hierarchy.

Output

The node outputs JSON data representing the updated role object returned from the Nestr API. This typically includes the role's ID, updated labels, parent ID, and other metadata reflecting the current state after the update.

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 nestrOAuth2Api credential configured in n8n.
  • The workspace must exist and be accessible with the provided credentials.
  • The role to update must already exist within the specified workspace.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent workspace ID will cause the API request to fail.
    • Specifying a role that does not exist or is not part of the workspace will result in errors.
    • Incorrectly formatted labels (e.g., missing commas) may lead to unexpected label assignments.

  • Error messages:

    • "Role not found" — Verify the role ID and workspace association.
    • "Unauthorized" or "Authentication failed" — Check that the OAuth2 credentials are valid and have sufficient permissions.
    • "Invalid input" — Ensure that labels are comma-separated strings and parent ID is a valid role identifier.

Resolving these usually involves verifying IDs, ensuring proper formatting of inputs, and confirming API credentials.

Links and References

Discussion