Actions100
- Activity Log Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Folder Actions
- IP Address Actions
- List Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
Overview
This node integrates with the Hudu REST API to manage various resources, including companies. Specifically, the "Delete" operation for the "Company" resource allows users to remove a company record from their Hudu account by specifying its unique ID. This is useful in scenarios where companies are no longer relevant or need to be cleaned up from the system.
Practical examples:
- Automatically deleting companies that have been marked as inactive in another system.
- Cleaning up test or duplicate company entries during data synchronization workflows.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique numeric identifier of the company to delete. |
Output
The node outputs a JSON array containing the result of the delete operation for each input item processed. Each output item corresponds to an input item and includes the response from the Hudu API after attempting to delete the specified company.
If the deletion is successful, the output typically contains confirmation details or an empty object indicating success. If there is an error (e.g., company not found), the output will include an error message if "Continue On Fail" is enabled.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Hudu REST API.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL for the Hudu API must be set in the node credentials.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Company ID will cause the API to return an error.
- Missing or incorrect API key credentials will prevent authentication.
- Network connectivity issues can cause request failures.
Error messages:
"The resource \"companies\" is not known!"— indicates an invalid resource parameter; ensure "companies" is selected.- API errors returned from Hudu (e.g., 404 Not Found) usually mean the company ID does not exist.
Resolutions:
- Verify the Company ID is correct and exists in Hudu.
- Check that the API key credential is properly configured and has sufficient permissions.
- Enable "Continue On Fail" in the node settings to handle errors gracefully within workflows.
Links and References
- Hudu API Documentation (for detailed API endpoints and responses)
- n8n documentation on HTTP Request Authentication (general guidance on setting up API credentials)