AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation updates a Managed Service Provider (MSP) under the "Distributors" resource. It allows users to modify details of an MSP, specifically by sending a JSON body with updated information such as distributor SKUs associated with the MSP's parent organization. This is useful in scenarios where distributors need to manage or synchronize their MSP data programmatically, for example, updating product SKUs or organizational relationships.

Practical examples include:

  • Updating the list of SKUs that an MSP’s parent organization distributes.
  • Modifying hierarchical relationships within distributor-managed MSPs.
  • Automating MSP data synchronization from external systems into the platform.

Properties

Name Meaning
Body A JSON object representing the update payload for the MSP. Typically includes nested fields such as msp.parent_organization.distributor_skus, which is an array of SKU identifiers or null values. This defines what aspects of the MSP are being updated.
Id The numeric identifier of the MSP to update. This specifies which MSP record the update applies to.

Output

The node outputs JSON data reflecting the response from the update operation. This typically includes confirmation of the updated MSP data or error information if the update failed. The exact structure depends on the API response but generally contains the updated MSP details.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the external service managing distributors and MSPs.
  • The base URL for API requests is set to "https://api.dnsfilter.com" as per the bundled source, indicating the node interacts with this external API.
  • Proper configuration of the API key credential in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing MSP ID (Id property) will cause the update to fail.
    • Malformed JSON in the Body property can lead to request errors.
    • Authentication failures due to incorrect or missing API credentials.
    • Network connectivity issues preventing access to the external API endpoint.
  • Error messages:

    • Errors related to invalid input typically indicate problems with the Body JSON structure or missing required fields.
    • Authorization errors suggest checking the API key credential setup.
    • HTTP errors like 404 may mean the MSP ID does not exist.

To resolve these, verify the MSP ID is correct, ensure the JSON body matches expected schema, and confirm API credentials are valid and have sufficient permissions.

Links and References

  • No direct links provided in the source code.
  • For more details, consult the API documentation of the external service at https://api.dnsfilter.com or the relevant distributor/MSP management API docs.

Discussion