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 the Nestr platform to manage projects within workspaces. Specifically, the "Update Project" operation allows users to modify existing project details such as title, description, labels, and associations like parent or circle IDs.

This node is beneficial in scenarios where automated workflows need to keep project information up-to-date based on external triggers or data changes. For example, a team might update project titles or descriptions automatically when certain conditions are met, or synchronize project metadata from other systems.

Practical examples:

  • Automatically updating a project's description when a related document is modified.
  • Changing project labels based on status updates from another tool.
  • Associating a project with a different circle or parent item dynamically.

Properties

Name Meaning
Workspace Name or ID Selects the workspace containing the project. Can be chosen from a list or specified by ID.
Project ID The unique identifier of the project to update.
Title The new title for the project.
Description The new description text for the project.
Circle ID The ID of the circle to associate with the project.
Additional Fields A collection of optional fields:
- Labels: Comma-separated list of labels to assign.
- Parent ID: ID of a parent item to link as ancestor.

Output

The node outputs JSON data representing the updated project object returned from the Nestr API. This includes all relevant project properties after the update, such as title, description, labels, workspace association, and any hierarchical relationships.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Nestr API using OAuth2 authentication (an API key credential).
  • The node depends on the Nestr API endpoints for projects and workspaces.
  • The "Workspace Name or ID" property uses a dynamic options loader that fetches available workspaces via the API.

Troubleshooting

  • Common issues:

    • Invalid or missing project ID will cause the update request to fail.
    • Incorrect workspace ID may result in authorization errors or not finding the project.
    • Labels must be provided as a comma-separated string; improper formatting could lead to unexpected label assignments.
    • If the circle ID or parent ID does not exist or is invalid, the API may reject the update.

  • Error messages:

    • Errors from the API typically include messages about resource not found or permission denied.
    • Network or authentication failures will prevent the request from completing.

  • Resolutions:

    • Verify that the project ID exists and belongs to the specified workspace.
    • Ensure the API credentials have sufficient permissions.
    • Format labels correctly as comma-separated values without extra spaces.
    • Confirm that referenced circle and parent IDs are valid within the workspace context.

Links and References

Discussion