AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation allows revoking an API key by its identifier. It is useful in scenarios where you need to invalidate an existing API key, for example, when a key is compromised, no longer needed, or should be rotated for security reasons. By revoking the key, you prevent further access using that key.

Practical examples include:

  • Automatically revoking API keys after a certain period.
  • Revoking keys when a user is deactivated or removed.
  • Managing API key lifecycle within automated workflows.

Properties

Name Meaning
Id The unique numeric identifier of the API key to revoke

Output

The output JSON will typically contain information about the result of the revoke operation, such as success confirmation or error details. The exact structure depends on the API response but generally includes status indicators and possibly metadata about the revoked key.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authentication with the external service managing the API keys.
  • The node uses a base URL pointing to the DNSFilter API endpoint (https://api.dnsfilter.com).
  • Proper configuration of the API authentication credentials in n8n is necessary.

Troubleshooting

  • Invalid Id: If the provided API key ID does not exist or is invalid, the node may return an error indicating the key was not found. Verify the ID before running the node.
  • Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Ensure the API key credential is correctly set up.
  • Network Issues: Connectivity problems to the API endpoint can cause timeouts or request failures. Check network access and proxy settings if applicable.
  • Permission Denied: The API key used for authentication must have sufficient permissions to revoke other keys.

Links and References

Discussion