AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation allows users to create a new Block Page within the AvantGuard DNSFilter system. Block Pages are customizable pages shown to end-users when access to certain websites or resources is blocked by the DNS filtering service. This operation is useful for organizations wanting to personalize the block experience with their branding, contact information, and other relevant details.

Practical examples include:

  • Creating a branded block page that displays the organization's name and logo.
  • Specifying a contact email address on the block page for users to request access or report issues.
  • Setting timestamps for creation and last update of the block page for administrative tracking.

Properties

Name Meaning
Additional Body Fields Optional fields to customize the block page content. Includes:
- Name The name of the block page.
- Organization Id Numeric ID of the organization owning the block page.
- Block Org Name The organization name displayed on the block page.
- Block Email Addr Contact email address shown on the block page.
- Block Logo Uuid UUID of a custom logo image uploaded externally (e.g., uploadcare.com) to display.
- Created At Timestamp string indicating when the block page was created.
- Updated At Timestamp string indicating the last time the block page was updated.

Output

The node outputs JSON data representing the newly created block page resource as returned by the API. This typically includes all the properties sent in the request along with any additional metadata assigned by the server such as unique identifiers or status fields.

No binary data output is involved in this operation.

Dependencies

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

Troubleshooting

  • Common Issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Providing invalid field values (e.g., non-numeric organization ID) may result in validation errors.
    • Network connectivity problems can prevent successful API calls.
  • Error Messages:

    • Authentication errors typically indicate incorrect or missing API keys; verify credential setup.
    • Validation errors from the API will specify which fields are incorrect or missing; review input property values.
    • Timeout or connection errors suggest network issues; check internet connectivity and firewall settings.

Links and References

Discussion