Search Hashes

web_risk.search_hashes
ActionGoogle Cloudconnection required

Calls Web Risk GET /v1/hashes:search.

Gets the full hashes that match the requested hash prefix. This is used after a hash prefix is looked up in a threatList and there is a match.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Web Risk
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
hash_prefix
URL-safe base64 hash prefix from a local threat-list lookup. Optional.
stringNo———
threat_types
Threat lists to search. Defaults to MALWARE and SOCIAL_ENGINEERING. One of MALWARE, SOCIAL_ENGINEERING, UNWANTED_SOFTWARE, SOCIAL_ENGINEERING_EXTENDED_COVERAGE, or a list of them.
arrayNo—array of string—

Output

One shape.

result

FieldTypeExample
ok
boolean—
negativeExpireTime
string—
threats
array—
{
  "negativeExpireTime": "",
  "ok": false,
  "threats": []
}

Related Google Web Risk nodes

See Search Hashes run in a workflow.

In a technical demo we add the Google Web Risk connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.