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
This node allows you to delete a specific Relation in the Hudu system by its unique ID. It is useful in scenarios where you need to programmatically remove relationships between entities (such as contacts, companies, or assets) managed within Hudu. For example, if an integration or automation detects that a relationship is no longer valid, this node can be used to clean up the data accordingly.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | ID of the Relation to be deleted. This uniquely identifies which relation will be removed from Hudu. |
Output
- The node outputs a JSON object indicating the result of the deletion operation. The exact structure may depend on the API's response, but typically it would include confirmation of deletion or relevant status information.
- No binary data is output by this operation.
Dependencies
- External Service: Requires access to a Hudu instance with API enabled.
- API Key/Credentials: Needs n8n credentials named
avantguardHuduApiwith at least thebaseUrlproperty configured. - n8n Configuration: Ensure the credential is set up and accessible to the workflow.
Troubleshooting
- Missing or Invalid Credentials: If the required credentials are not provided or incorrect, the node will fail to connect to the Hudu API. Make sure the
avantguardHuduApicredential is correctly configured. - Invalid Relation ID: Providing an ID that does not exist or has already been deleted will likely result in an error from the API, such as "Relation not found".
- Permission Issues: The API key used must have permission to delete relations; otherwise, you may receive authorization errors.
- Network/Connectivity Errors: If n8n cannot reach the Hudu API endpoint (e.g., due to network issues or incorrect base URL), the node will throw connection errors.