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 Delete Magic Dash operation for the "Magic Dash" resource in this custom n8n node is designed to delete a specific Magic Dash item from an external system (presumably Hudu, as suggested by the node name). This operation requires you to specify both the title and company name of the Magic Dash item you wish to remove.
Common scenarios:
- Automating the cleanup of outdated or incorrect Magic Dash items.
- Integrating with other workflows where Magic Dash items need to be programmatically deleted based on certain triggers or conditions.
Practical example:
You might use this node in a workflow that reviews Magic Dash items nightly and deletes those that match certain criteria (e.g., obsolete dashboards for a given company).
Properties
| Name | Type | Meaning |
|---|---|---|
| Title | String | The title attribute of the Magic Dash Item to be deleted. |
| Company Name | String | The company name attribute of the Magic Dash Item to be deleted. |
Output
The output structure is not explicitly defined in the provided code. However, typically for a delete operation:
- If successful, the node may return a confirmation message or status indicating the deletion was successful.
- If unsuccessful, it may return an error message or status.
Example output (typical for delete operations):
{
"success": true,
"message": "Magic Dash item deleted successfully."
}
or, in case of failure:
{
"success": false,
"error": "Item not found."
}
Dependencies
- External Service: Requires access to the Hudu API (or a compatible service).
- API Credentials: You must configure the
avantguardHuduApicredential in n8n, which should include at least thebaseUrland likely an API key or token. - n8n Configuration: Ensure the credentials are set up in your n8n instance under the correct name.
Troubleshooting
Common issues:
- Missing or incorrect credentials: If the
avantguardHuduApicredential is not configured or contains invalid information, the node will fail to connect to the API. - Incorrect Title or Company Name: If the specified Magic Dash item does not exist (wrong title or company name), the API may return an error such as "Item not found."
- Insufficient permissions: The API key used may lack permission to delete Magic Dash items, resulting in authorization errors.
Common error messages and resolutions:
"401 Unauthorized": Check your API credentials and ensure they have delete permissions."404 Not Found": Verify that the Title and Company Name exactly match an existing Magic Dash item."400 Bad Request": Ensure all required fields are filled and correctly formatted.
Links and References
- n8n Documentation
- Hudu API Documentation (if applicable)
- AvantGuard n8n Nodes GitHub (if available)