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 is designed to interact with the "Companies" resource in the AvantGuard Hudu API, specifically to unarchive a company by its ID. The "Put Companies Id Unarchive" operation allows users to restore a previously archived company, making it active again within the system.
Common scenarios:
- Restoring companies that were archived by mistake.
- Re-enabling access to company data for reporting or operational needs.
- Automating workflows where companies may be temporarily archived and later restored.
Practical example:
A user can set up an n8n workflow to automatically unarchive a company when certain conditions are met (e.g., upon receiving a support request).
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | ID of the company to unarchive. This is required and identifies which company will be restored from the archive state. |
Output
The output will contain a JSON object representing the unarchived company. The structure typically includes fields such as the company's ID, name, status, and other relevant details as returned by the Hudu API after the unarchive operation.
Note: The exact structure depends on the API response, but you can expect standard company information.
Dependencies
- External Service: Requires access to the AvantGuard Hudu API.
- API Credentials: You must configure the node with valid
avantguardHuduApicredentials, including the base URL (baseUrl) and any necessary authentication tokens. - n8n Configuration: Ensure the credentials are set up in n8n under the appropriate credential type.
Troubleshooting
Common issues:
- Invalid Company ID: If the provided ID does not correspond to an existing or archived company, the API may return a "Not Found" or similar error.
- Missing Credentials: If credentials are not configured or are incorrect, authentication errors will occur.
- Permission Denied: The API key used may lack permission to unarchive companies.
Error messages and resolutions:
"401 Unauthorized": Check your API credentials and ensure they are correct and have sufficient permissions."404 Not Found": Verify that the company ID exists and is currently archived."400 Bad Request": Ensure all required parameters are provided and correctly formatted.
Links and References
- Hudu API Documentation (for reference on company endpoints)
- n8n Documentation: Custom Nodes
- AvantGuard Hudu Integration Guide