AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation updates the membership details of a user within a distributor context. It is useful when you need to modify the permissions or roles assigned to a specific user by updating their membership information, such as organization permission IDs. Practical examples include changing access levels for users in a distributor's system or managing user roles programmatically.

Properties

Name Meaning
Body JSON object representing the membership update payload. Typically includes fields like membership with nested properties such as organization_permission_ids, which is an array of permission identifiers to assign to the user.
Id The unique numeric identifier of the user whose membership is being updated.

Output

The output will contain a JSON object reflecting the result of the membership update operation. This typically includes confirmation of the updated user membership data or status information returned from the API. There is no indication that binary data is involved in this operation.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The node uses a base URL pointing to the DNSFilter API endpoint (https://api.dnsfilter.com).
  • Proper configuration of the API credentials and network access to the external service is necessary.

Troubleshooting

  • Common issues:
    • Invalid or missing user ID can cause the update to fail.
    • Malformed JSON in the Body property may lead to request errors.
    • Insufficient permissions or invalid API credentials will result in authorization errors.
  • Error messages:
    • "User not found" indicates the provided user ID does not exist.
    • "Invalid membership data" suggests the JSON body structure is incorrect.
    • "Unauthorized" or "Authentication failed" means the API key or credentials are invalid or missing.
  • Resolutions:
    • Verify the user ID is correct and exists.
    • Ensure the JSON body matches the expected schema.
    • Confirm API credentials are properly set up and have required permissions.

Links and References

Discussion