Actions3
- File Actions
- Website Actions
Overview
This node integrates with a virus scanning service to detect malware and malicious content. Specifically, the "Website - Scan" operation allows users to scan a given website URL for threats such as viruses, malware, or other harmful content. This is useful in scenarios where you want to verify the safety of websites before allowing access, automate security checks on URLs shared within your systems, or monitor external links for potential risks.
For example, you could use this node to:
- Automatically scan URLs submitted through a form to ensure they are safe.
- Periodically check important partner websites for security issues.
- Integrate into a workflow that blocks or flags suspicious URLs before further processing.
Properties
| Name | Meaning |
|---|---|
| URL | The website URL to scan for malicious content and threats. Must be a valid HTTP or HTTPS address. |
Output
The node outputs an array of JSON objects, each representing the scan result for the input item. The json output contains the detailed response from the virus scanning API about the scanned website. This typically includes information about detected threats, scan status, and any relevant metadata returned by the service.
No binary data output is produced for the website scan operation.
Dependencies
- Requires an API key credential for the virus scanning service (Cloudmersive).
- The node makes authenticated HTTP POST requests to the Cloudmersive Virus Scan API endpoint for websites.
- Proper configuration of the API key credential in n8n is necessary for successful operation.
Troubleshooting
Common Issues:
- Invalid or missing URL input will cause the scan to fail.
- Network connectivity problems or incorrect API credentials will result in authentication errors.
- The API may reject URLs that do not start with http:// or https://.
Error Messages:
- Errors thrown by the node include details from the underlying API error response.
- Authentication failures indicate misconfigured or expired API keys.
- Validation errors usually point to malformed URLs or unsupported input formats.
Resolutions:
- Ensure the URL property is correctly set and includes the protocol.
- Verify the API key credential is properly configured and active.
- Check network access to the Cloudmersive API endpoints.