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 retrieves a specific Asset Password by its ID from the AvantGuard Hudu system. It is useful in scenarios where you need to programmatically access or reference a particular password stored within your asset management system, such as for automated credential retrieval, auditing, or integration with other workflows.
Example use cases:
- Fetching credentials for deployment scripts.
- Integrating with monitoring tools that require dynamic access to passwords.
- Automating password audits or compliance checks.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | ID of the requested Password. This identifies which Asset Password record to retrieve from the system. |
Output
The output will be a JSON object containing the details of the requested Asset Password. The exact structure depends on the API response, but typically includes fields such as the password's value, associated asset information, and metadata.
Example output:
{
"id": 123,
"password": "examplePassword",
"assetId": 456,
"description": "Database root password",
"createdAt": "2024-06-01T12:00:00Z",
"updatedAt": "2024-06-10T08:30:00Z"
}
Note: Actual fields may vary based on the Hudu API schema.
Dependencies
- External Service: Requires access to an AvantGuard Hudu instance with API enabled.
- API Credentials: Needs valid
avantguardHuduApicredentials configured in n8n, including the base URL and authentication token. - n8n Configuration: Ensure the credentials are set up under the name
avantguardHuduApi.
Troubleshooting
- Invalid ID Error: If the provided ID does not exist, the node may return a "Not Found" or similar error. Double-check the ID value.
- Authentication Errors: If credentials are missing or incorrect, errors like "401 Unauthorized" or "403 Forbidden" may occur. Verify your API key and permissions.
- Connection Issues: Network problems or incorrect base URL configuration can result in connection timeouts or "Unable to reach server" errors.