Nestr icon

Nestr

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

Actions29

Overview

This node allows you to manage posts within the Nestr collaboration platform, specifically enabling deletion of posts in a selected workspace. It is useful when you want to programmatically remove outdated or irrelevant posts from your project management environment.

A practical example: You have automated workflows that archive completed tasks and want to clean up associated posts automatically by deleting them once they are no longer needed.

Properties

Name Meaning
Workspace Name or ID Select the workspace where the post exists. Choose from a list of available workspaces or specify an ID using an expression.
Additional Fields Optional extra parameters for the post deletion request:
- Labels: Comma-separated list of labels (not typically used for delete but available).
- Parent ID: Parent item ID (optional context).

Output

The output JSON contains the response from the Nestr API after attempting to delete the specified post. Typically, this will be confirmation data indicating successful deletion or details about the deleted post.

No binary data output is produced by this operation.

Dependencies

  • Requires an OAuth2 API credential configured for authenticating with the Nestr API.
  • The node depends on the Nestr API endpoints to perform operations on posts.
  • The workspace list is dynamically loaded via an API call to populate the workspace selection dropdown.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent workspace ID or post ID will cause the deletion to fail.
    • Insufficient permissions or expired authentication tokens can result in authorization errors.
    • Network connectivity problems may prevent API requests from completing.

  • Error messages:

    • Errors returned from the API will be included in the node's output if "Continue On Fail" is enabled.
    • Typical error messages include "Not Found" if the post does not exist or "Unauthorized" if credentials are invalid.

  • Resolutions:

    • Verify the workspace and post IDs are correct and accessible.
    • Ensure the OAuth2 credentials are valid and have necessary scopes.
    • Check network connectivity and retry the operation.

Links and References

Discussion