AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node updates an existing Agent Local User by sending specified update parameters to the corresponding API. It is useful in scenarios where you need to modify user details such as permissions, roles, or other attributes associated with a local user on an agent system. For example, you might use this node to change access rights for a user or update their profile information programmatically within an automation workflow.

Properties

Name Meaning
Id The unique identifier of the Agent Local User to update.
Agent Local User JSON object containing the update parameters for the Agent Local User. This should include the fields and values you want to modify for the user.

Output

The node outputs JSON data representing the response from the API after attempting to update the Agent Local User. This typically includes confirmation of the update, the updated user details, or error information if the update failed. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard DNSFilter API.
  • The node uses the base URL https://api.dnsfilter.com for its API calls.
  • Proper configuration of the API authentication credential in n8n is necessary for successful operation.

Troubleshooting

  • Common issues:

    • Invalid or missing user ID (Id property) will cause the update to fail.
    • Malformed JSON in the Agent Local User property can lead to request errors.
    • Authentication failures due to incorrect or expired API credentials.
    • Network connectivity issues preventing access to the API endpoint.
  • Error messages and resolutions:

    • "Unauthorized" or "Authentication failed": Verify that the API key credential is correctly configured and valid.
    • "User not found": Check that the provided Id corresponds to an existing Agent Local User.
    • "Invalid JSON body": Ensure the JSON in the Agent Local User field is well-formed and matches the expected schema.
    • Timeout or network errors: Confirm network connectivity and API availability.

Links and References

Discussion