Search Uris

web_risk.search_uris
ActionGoogle Cloudconnection required

Calls Web Risk GET /v1/uris:search.

This method is used to check whether a URI is on a given threatList. Multiple threatLists may be searched in a single query.

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, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
uri
The URI to check, e.g. {{ $steps.extract.link }}. Required — the API rejects a search that names no URI.
stringYes———
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—
threat
object—
{
  "ok": false,
  "threat": {}
}

Related Google Web Risk nodes

See Search Uris 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.