AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation allows users to check the status of a bulk update job related to Networks. It is useful in scenarios where multiple network configurations or settings are updated simultaneously, and you want to monitor the progress or result of that bulk update. For example, after initiating a bulk update to change firewall rules across many networks, this operation can be used to query the current status of that job by its ID.

Properties

Name Meaning
Id The unique identifier of the bulk update job whose status you want to check. This is required to retrieve the status information for that specific job.

Output

The output will contain JSON data representing the status of the specified bulk update job. This typically includes details such as whether the job is still running, completed successfully, failed, or any other relevant metadata about the bulk update process. The exact structure depends on the API response but generally provides insight into the progress and outcome of the bulk update.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authentication with the external service managing the Networks.
  • The node uses a base URL pointing to the DNSFilter API endpoint (https://api.dnsfilter.com), indicating it interacts with the AvantGuard DNSFilter service.
  • Proper configuration of the API key credential within n8n is necessary for successful requests.

Troubleshooting

  • Invalid or missing Id: If the provided bulk update job ID is incorrect or not found, the node may return an error or empty status. Ensure the ID is correct and corresponds to an existing bulk update job.
  • Authentication errors: If the API key credential is invalid or missing, the node will fail to authenticate. Verify that the API key is correctly set up in n8n credentials.
  • Network issues: Connectivity problems to the API endpoint can cause request failures. Check internet connection and API service availability.
  • API rate limits: Excessive requests might lead to throttling. Monitor usage and respect API limits.

Links and References

Discussion