AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation allows adding a membership to a user within the "Distributors" resource. It is designed to update a specific user's membership details by specifying permission IDs associated with an organization. This can be useful in scenarios where you need to programmatically manage user roles or permissions within a distributor's system, such as granting access rights or updating organizational memberships.

Practical examples include:

  • Adding new permission sets to a user when they join a new team or project.
  • Automating membership updates based on external triggers or workflows.
  • Managing user access levels dynamically without manual intervention.

Properties

Name Meaning
Body JSON object containing membership details. Specifically, it includes organization_permission_ids, which is an array of permission IDs to assign to the user. Example structure: { "membership": { "organization_permission_ids": [<permission_id_1>, <permission_id_2>] } }
Id The unique numeric identifier of the user to whom the membership will be added.

Output

The output contains a JSON object representing the result of the membership addition operation. This typically includes confirmation of the updated membership status or details about the user’s new permissions. The exact structure depends on the API response but generally reflects the updated user membership data.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication with the external service managing distributors and users.
  • The node uses a base URL endpoint (not explicitly shown here) to send requests.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Invalid User ID: If the provided user ID does not exist, the API may return an error indicating the user was not found. Verify the user ID before running the node.
  • Malformed Body JSON: Ensure the JSON in the Body property is correctly formatted and includes valid permission IDs. Invalid JSON or missing required fields will cause request failures.
  • Permission Issues: If the API key lacks sufficient privileges to modify user memberships, the operation will fail. Confirm that the API key has appropriate permissions.
  • Network or Authentication Errors: Check network connectivity and API key validity if requests fail due to authentication or connection issues.

Links and References

  • Refer to the external API documentation for detailed information on the membership object and permission IDs.
  • Consult n8n documentation on how to configure API credentials and use JSON input properties effectively.

Discussion