Hypris icon

Hypris

Interact with the Hypris API

Actions16

Overview

This node interacts with the Hypris API to manage various resources such as workspaces, databases, items, properties, views, and resource items. Specifically, for the Item - Delete operation, it deletes one or more items identified by their IDs within a specified workspace and database.

Typical use cases include:

  • Automating cleanup of outdated or irrelevant items in a database.
  • Bulk deletion of multiple items based on external triggers or workflows.
  • Integrating Hypris item management into larger automation pipelines where item lifecycle is controlled programmatically.

For example, you might use this node to delete several items from a project database after they are marked as completed or obsolete.

Properties

Name Meaning
Workspace Name or ID The workspace containing the database and items to operate on. Choose from a list or specify an ID.
Database Name or ID The database within the workspace where the items exist. Choose from a list or specify an ID.
Item IDs Comma-separated list of item IDs to delete.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will be confirmation details or status information returned by the Hypris API about the deleted items.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Hypris API.
  • Needs network access to the Hypris API endpoint.
  • The node dynamically loads options for workspaces and databases via API calls, so proper permissions and valid credentials are necessary.
  • No additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Invalid or missing workspace or database IDs can cause failures.
    • Incorrectly formatted item IDs (e.g., not comma-separated) may lead to errors.
    • Insufficient permissions or expired API credentials will prevent successful deletion.
    • Network connectivity problems to the Hypris API endpoint.

  • Error messages:

    • Errors during option loading (workspaces/databases) will log messages like "Failed to load databases" or similar.
    • API request failures will throw errors that include the HTTP response message; ensure credentials and IDs are correct.
    • If the node is set to continue on fail, errors will appear in the output JSON under an error field.

  • Resolutions:

    • Verify workspace and database selections are valid and accessible.
    • Confirm item IDs are correctly formatted and exist.
    • Check API credentials and renew if expired.
    • Ensure stable network connection to the Hypris API.

Links and References

Discussion