Actions100
- Activity Logs Actions
- Articles Actions
- 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
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation archives a specific Asset belonging to a given Company by updating its status via an API call. It is useful in scenarios where you need to programmatically mark an asset as archived within a company's asset management system, for example, when decommissioning equipment or retiring digital assets.
Practical examples include:
- Archiving outdated hardware assets linked to a company.
- Marking software licenses or subscriptions as inactive.
- Managing lifecycle states of company assets automatically based on business rules.
Properties
Name | Meaning |
---|---|
Id | The identifier of the Asset to be archived. This is a required numeric value. |
Company Id | The identifier of the parent Company that owns the Asset. This is a required numeric value. |
Output
The node outputs JSON data representing the result of the archive operation on the specified Asset. This typically includes confirmation of the asset's updated status or details about the archived asset. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authentication with the external service managing companies and assets.
- The base URL for the API must be configured in the node credentials.
- Depends on the
@avantguardllc/n8n-openapi-node
package for building request properties from the OpenAPI specification.
Troubleshooting
- Missing or invalid Id/Company Id: Ensure both identifiers are provided and valid numbers; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or API errors: Check connectivity and API endpoint availability; ensure the base URL is correct.
- Unexpected response structure: Confirm that the API version matches the expected OpenAPI spec used by the node.
Links and References
- AvantGuard API Documentation (hypothetical link)
- n8n Custom Node Development