Actions16
Overview
This node allows you to create a new property in a specified database within a workspace using the Hypris API. Properties define the schema or fields of items stored in a database, such as text fields, numbers, dates, dropdowns, and more.
Typical use cases include:
- Automating the setup of databases by programmatically adding new fields.
- Dynamically adjusting database schemas based on workflow logic.
- Integrating with other systems that require creating or updating data structures in Hypris.
For example, you might create a "Status" property of type "Dropdown" to track item progress, or a "Due Date" property of type "Date" for task management.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | The workspace where the database resides. Choose from a list or specify an ID via expression. |
| Database Name or ID | The database in which to create the new property. Choose from a list or specify an ID via expression. |
| Property Type | The type of property to create. Options include: Auto ID, Boolean, Checklist, Comments, Created At, Date, Date Range, Dropdown, Email, Files, Formula, ID, Link, Location, Long Text, Number, People, Phone, Random ID, Rating, Relation, Reverse Relation, Rich Text, Status, Teleport, Text, Time, Time Tracker, Updated At. |
| Property Title | The title (name) of the new property. |
Output
The node outputs JSON data representing the newly created property object returned by the Hypris API. This typically includes details such as the property ID, type, title, and any metadata associated with it.
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.
- Uses internal helper methods to load options dynamically (e.g., workspaces, databases).
- Requires proper configuration of credentials in n8n with base URL, username, and password for Hypris.
Troubleshooting
Common issues:
- Invalid or missing workspace or database IDs can cause failures.
- Insufficient permissions or incorrect API credentials will result in authentication errors.
- Network connectivity problems may prevent API requests.
- Selecting incompatible property types or invalid titles may cause API validation errors.
Error messages:
- Authentication errors usually indicate invalid credentials; verify API keys and user/password.
- "Failed to load databases" or similar messages suggest issues fetching dependent resources; check workspace ID validity.
- Validation errors from the API about property type or title should be resolved by ensuring correct input values.
Links and References
- Hypris API Documentation (hypothetical link)
- n8n Expressions Documentation
- n8n Credential Management
Note: This summary is based on static analysis of the provided source code and property definitions without runtime execution.