Cloudmersive Virus Scan icon

Cloudmersive Virus Scan

Scan files, websites, and cloud storage for malware via Cloudmersive

Actions3

Overview

This node integrates with the Cloudmersive Virus Scan API to scan files or websites for malware and malicious content. It is useful in automation workflows where you need to ensure that files or URLs are safe before further processing, sharing, or storage. For example, it can be used to automatically scan email attachments, uploaded documents, or links submitted by users to detect viruses or threats.

Specifically, the "File" resource with the "Scan" operation scans a binary file for viruses using a straightforward virus scanning endpoint.

Properties

Name Meaning
Binary Property Name The name of the binary property in the input data that contains the file to be scanned.

Output

The node outputs an array of JSON objects, each representing the scan result for one input item. The json output field contains the response from the Cloudmersive Virus Scan API, which includes details about whether the file was found to contain viruses or other threats.

No binary data is output by this node; it only returns JSON metadata describing the scan results.

Dependencies

  • Requires an API key credential for the Cloudmersive Virus Scan service.
  • The node uses the Cloudmersive Virus Scan REST API endpoints.
  • Proper configuration of the API key credential in n8n is necessary for authentication.

Troubleshooting

  • Common issues:

    • Missing or invalid API key credential will cause authentication errors.
    • Specifying a non-existent binary property name will result in no file being sent for scanning.
    • Network connectivity problems may cause request failures.
  • Error messages:

    • Authentication errors typically indicate invalid or missing API credentials.
    • Errors related to file upload usually mean the specified binary property does not exist or is empty.
    • API rate limits or quota exceeded errors may occur if usage exceeds the allowed limits.

To resolve these:

  • Ensure the API key credential is correctly set up and valid.
  • Verify the binary property name matches the actual binary data property in the input.
  • Check network connectivity and API usage quotas.

Links and References

Discussion