Actions16
Overview
This node integrates with the Hypris API to perform various operations on different resources such as databases, items, properties, views, workspaces, and resource items. Specifically, for the Database - Get Many operation, it retrieves multiple database records within a specified workspace. This is useful when you want to list or process all databases available in a particular workspace.
Practical examples include:
- Automating synchronization of databases from Hypris into another system.
- Fetching all databases to display or analyze their metadata.
- Using the retrieved databases as input for further processing or filtering workflows.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | The workspace to operate on. Choose from a dropdown list of available workspaces or specify an ID via expression. |
Output
The output consists of JSON objects representing each database retrieved from the specified workspace. Each JSON object contains the database's details such as its name, ID, and other metadata as returned by the Hypris API.
The output structure is an array of these JSON objects, one per database found.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Hypris API.
- The node uses HTTP Basic Authentication with username and password credentials.
- The base URL for the Hypris API must be configured in the credentials.
- The node depends on n8n's HTTP request helper to communicate with the Hypris API.
Troubleshooting
Common issues:
- Invalid or missing workspace ID: Ensure the workspace ID is correctly selected or provided.
- Authentication errors: Verify that the API credentials (username, password, base URL) are correct and have sufficient permissions.
- Network or API endpoint errors: Check network connectivity and that the Hypris API service is reachable.
Error messages:
- "Failed to load databases: [error message]" indicates a problem fetching databases from the API. Check credentials and workspace ID.
- Request timeouts or connection refused errors suggest network issues or incorrect API URL configuration.
To resolve errors, confirm all required parameters are set, credentials are valid, and the Hypris API is operational.
Links and References
- Hypris API Documentation (hypothetical link as no direct link was provided)
- n8n Expressions Documentation
- n8n HTTP Request Node (for understanding underlying HTTP calls)