AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve users associated with a specific Asset. It is designed to fetch detailed user information linked to an asset, which can be useful in scenarios such as auditing asset access, managing permissions, or integrating asset-user data into workflows.

Practical examples include:

  • Automatically retrieving and processing the list of users who have access to a particular asset.
  • Filtering or sorting asset users based on custom query parameters for reporting or compliance.
  • Integrating asset user data into other systems like CRM or IT management tools.

Properties

Name Meaning
X USER ID The User Id header value required by the API to identify the user making the request.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Query condition string.
- Skip: Number of records to skip.
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The node outputs JSON data representing the users retrieved for the specified asset. The structure typically includes user details such as user IDs, names, roles, or other metadata as provided by the API response.

If binary data were returned (not indicated here), it would represent file attachments or similar content related to asset users, but this node focuses on JSON user data.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard ConnectSecure API.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for OpenAPI integration.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the X USER ID header; ensure it is provided and correctly formatted.
  • API authentication errors: Verify that the API key credential is valid and has necessary permissions.
  • Query parameter issues: Incorrectly formatted query conditions or invalid values for skip/limit/order_by may cause errors or unexpected results.
  • Network or connectivity problems: Ensure the base URL is reachable from the n8n instance.

Common error messages might include unauthorized access, bad request due to invalid query parameters, or not found if the asset or users do not exist.

Links and References

Discussion