Actions109
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Websites Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Users Actions
- Activity Logs Actions
- Articles Actions
Overview
The AvantGuard - Hudu node for n8n allows you to create ("post") new relations between entities in the Hudu system. This is useful for linking different types of records (such as Assets, Websites, Procedures, etc.) together, establishing relationships that can be referenced or queried later.
Common scenarios:
- Linking a Website to an Asset to indicate hosting.
- Associating a Procedure with a Company for documentation purposes.
- Creating bidirectional (inverse) relationships between two entities for easier navigation and data integrity.
Practical example:
You might use this node to automatically relate a newly created Password record to its parent Asset, ensuring all relevant information is connected within Hudu.
Properties
| Name | Type | Meaning |
|---|---|---|
| Toable Id | Number | The ID of the destination entity in the relation. |
| Toable Type | String | The type of the destination entity (e.g., Asset, Website, Procedure, AssetPassword, Company, Article). |
| Fromable Id | Number | The ID of the origin entity in the relation. |
| Fromable Type | String | The type of the origin entity (e.g., Asset, Website, Procedure, AssetPassword, Company, Article). |
| Description | String | A description explaining the relationship between the two entities. |
| Is Inverse | Boolean | If true, also creates the inverse relation; indicates if this relation is the inverse. |
All these properties are grouped under Additional Body Fields and are optional but typically required for meaningful relations.
Output
The node returns the JSON response from the Hudu API after creating the relation. The structure will generally include details about the created relation, such as IDs, types, and any metadata provided.
If the API supports binary responses, they would represent the raw data returned by Hudu, but for this operation, output is expected to be JSON only.
Dependencies
- External Service: Requires access to a Hudu instance with API enabled.
- API Key: Needs valid credentials (
avantguardHuduApi) configured in n8n. - Environment Variable: The base URL for your Hudu instance must be set in the credentials as
baseUrl.
Troubleshooting
Common issues:
- Missing or invalid credentials: Ensure the
avantguardHuduApicredential is correctly set up in n8n. - Invalid entity IDs or types: Double-check that the IDs and types correspond to existing records in Hudu.
- Insufficient permissions: The API key used must have permission to create relations.
Error messages:
"401 Unauthorized": Check your API key and permissions."404 Not Found": One of the specified entities does not exist."400 Bad Request": Required fields are missing or incorrectly formatted.