Nestr icon

Nestr

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

Overview

This node integrates with the Nestr platform to manage posts within workspaces. Specifically, the Get Post operation retrieves detailed information about a single post identified by its ID within a specified workspace. This is useful for workflows that need to fetch and process content or updates stored as posts in Nestr.

Practical examples include:

  • Automatically retrieving a post's details to send notifications or summaries.
  • Fetching post data to synchronize with other project management or communication tools.
  • Using post metadata (like labels or parent relationships) to organize or filter content dynamically.

Properties

Name Meaning
Workspace Name or ID Select the workspace to work with. Choose from a list of available workspaces or specify an ID via expression.
Additional Fields Optional extra parameters to refine the request:
- Labels Comma-separated list of labels to filter or tag the post.
- Parent ID The ID of a parent item to associate with the post.

Note: For the Get Post operation, the main required property is the workspace identifier. Additional fields like labels or parent ID may be used if supported by the API for filtering or context.

Output

The node outputs JSON data representing the retrieved post object. This includes all standard post properties as returned by the Nestr API, such as title, description, labels, parent relationships, creation dates, and any other metadata associated with the post.

If the post contains binary data (e.g., attachments), the node would handle it accordingly, but based on the static code analysis, this operation primarily returns JSON metadata about the post.

Dependencies

  • Requires an active connection to the Nestr API using OAuth2 authentication.
  • The node depends on the nestrApiRequest helper function to communicate with the Nestr REST API endpoints.
  • The user must configure valid credentials providing access to the Nestr workspace data.
  • The workspace must exist and be accessible by the authenticated user.

Troubleshooting

  • Common issues:

    • Invalid or missing workspace ID: Ensure the workspace exists and the ID is correct.
    • Insufficient permissions: The API token must have rights to read posts in the specified workspace.
    • Network or API errors: Check connectivity and Nestr service status.
  • Error messages:

    • "Workspace not found": Verify the workspace ID or name.
    • "Post not found": Confirm the post ID exists within the workspace.
    • Authentication errors: Re-authenticate or update the API credentials.

Resolving these typically involves verifying input parameters, checking API credentials, and ensuring the workspace and post IDs are valid.

Links and References

Discussion