AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation allows creating Managed Service Providers (MSPs) under Distributors by sending a structured JSON body to the relevant API endpoint. It is useful in scenarios where an organization needs to programmatically add MSP entities associated with distributor accounts, such as onboarding new partners or automating distributor management workflows.

Practical examples include:

  • Automatically creating MSP records when new partners sign up.
  • Integrating distributor MSP creation into larger automation pipelines for partner management.
  • Bulk creation of MSPs based on external data sources.

Properties

Name Meaning
Body A JSON object representing the MSP details to create. This includes nested fields such as msp and parent_organization, which may contain arrays like distributor_skus. The user must provide this JSON structure according to the API's expected schema.

Output

The node outputs JSON data representing the response from the API after attempting to create the MSP under the distributor. This typically includes confirmation details of the created MSP, any identifiers assigned, and status information.

If the API supports binary data output, it would be summarized here; however, based on the provided code and properties, the output is JSON only.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard DNSFilter service or a similar API endpoint managing distributors and MSPs.
  • The node depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled within the node for request building and validation.
  • Network access to the configured base URL (https://api.dnsfilter.com) is necessary.

Troubleshooting

  • Invalid JSON in Body: If the JSON provided in the "Body" property is malformed, the node will fail. Ensure the JSON syntax is correct and matches the expected schema.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly configured.
  • API Endpoint Issues: Network errors or incorrect base URL configuration can prevent successful requests. Confirm connectivity and endpoint correctness.
  • Missing Required Fields: The API may reject requests missing mandatory fields inside the JSON body. Review the API documentation to ensure all required data is included.

Links and References

Discussion