Short answer: Drop the "VirusTotal → Scan URL" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
URL to Scan url | url | Required | URL to Scan. e.g. "https://example.com" |
{"url": "https://example.com"}
{"data": {"id": "analysis-abc123","type": "analysis","links": {"self": "https://www.virustotal.com/api/v3/analyses/..."}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.