Actions16
Overview
This node interacts with the Hypris API to update an existing item within a specified workspace and database. It allows users to modify one or more fields of an item by specifying the item ID, its state (published or draft), and the new values for its properties.
Common scenarios where this node is beneficial include:
- Automating updates to records in a Hypris-managed database based on external triggers.
- Synchronizing data changes from other systems into Hypris items.
- Batch updating multiple items by looping over input data.
For example, you could use this node to update the status or details of a project task stored as an item in Hypris whenever a related event occurs in another system.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | The workspace containing the database and item to update. Choose from a list or specify an ID via expression. |
| Database Name or ID | The database within the workspace that contains the item. Choose from a list or specify an ID via expression. |
| Item ID | The unique identifier of the item to update. |
| Item State | The state of the item to update. Options are: "Published" or "Draft". |
| Item Fields | One or more fields to update on the item. Each field requires: - Property Name or ID: The property to update, selectable from the database's properties. - Value Name or ID: The new value for the property, selectable or typed. |
Output
The node outputs JSON data representing the updated item as returned by the Hypris API. The structure corresponds to the item’s properties after the update operation.
- If multiple items are processed, the output is an array of JSON objects, each representing an updated item.
- No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Hypris API.
- Needs network access to the Hypris API endpoint.
- Uses internal helper methods to load options dynamically for workspaces, databases, properties, and property values.
Troubleshooting
- Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Invalid IDs: Errors may occur if workspace, database, item, or property IDs are incorrect or do not exist. Verify these IDs carefully.
- Property value mismatches: When setting field values, ensure the value type matches the property type (e.g., select options must be valid choices).
- API request failures: Network issues or API downtime can cause request failures. Check connectivity and Hypris service status.
- Empty or missing required parameters: Make sure all required fields (workspaceId, databaseId, itemId, etc.) are provided.
If the node throws an error message indicating failure to load properties or databases, verify that the workspace and database IDs are correct and accessible with the given credentials.
Links and References
- Hypris API Documentation (example placeholder, replace with actual URL if available)
- n8n Expressions Documentation
- n8n Node Development Guide