AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation checks the status of a bulk destroy job for networks. It is useful when you have initiated a bulk deletion of multiple network entities and want to monitor or verify the progress and final result of that bulk operation. For example, after submitting a request to delete several networks at once, you can use this operation to query the job ID and get the current status, such as whether the job is still running, completed successfully, or failed.

Properties

Name Meaning
Id The ID of the bulk update job to check status on. This is a required string input that identifies the specific bulk destroy job whose status you want to retrieve.

Output

The output will contain JSON data representing the status of the bulk destroy job identified by the provided ID. This typically includes information such as the job's current state (e.g., pending, in progress, completed), any errors encountered, and possibly metadata about how many networks were affected. The exact structure depends on the API response but generally provides comprehensive details about the bulk destroy operation's progress and outcome.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The node uses a base URL pointing to https://api.dnsfilter.com.
  • Proper configuration of the API authentication token in n8n credentials is necessary to perform requests.

Troubleshooting

  • Invalid or missing job ID: If the provided job ID does not exist or is malformed, the API may return an error indicating the job was not found. Ensure the ID is correct and corresponds to an existing bulk destroy job.
  • Authentication errors: If the API key or authentication token is invalid or expired, the node will fail to connect. Verify that the API credentials are correctly set up and active.
  • Network issues: Connectivity problems or incorrect base URL configuration can cause request failures. Confirm network access and endpoint correctness.
  • API rate limits: Frequent polling of job status might hit rate limits imposed by the API provider. Implement appropriate delays or retries if needed.

Links and References

Discussion