Google Web Risk
Google CloudOAuth 2.0Connection test available
Web Risk (Google OAuth2).
OCNORA ships 4 typed Google Web Risk operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Web Risk
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Web Risk
Operations, grouped by what they do to your data.
Create and send 1
Read and search 2
Other operations 1
A sample Google Web Risk workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Web Risk trigger is needed.
- 2Search Hashesweb_risk.search_hashesGets 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.
- 3Compute Diffweb_risk.compute_diffGets the most recent threat list diffs. These diffs should be applied to a local database of hashes to keep it up-to-date.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 4
- Compute DiffGets the most recent threat list diffs. These diffs should be applied to a local database of hashes to keep it up-to-date.web_risk.compute_diff
- Create SubmissionCreates a Submission of a URI suspected of containing phishing content for review.web_risk.create_submission
- Search HashesGets 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.web_risk.search_hashes
- Search UrisThis method is used to check whether a URI is on a given threatList. Multiple threatLists may be searched in a single query.web_risk.search_uris
Google Web Risk questions
- How does OCNORA authenticate with Google Web Risk?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Web Risk?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Web Risk operation I need is not listed?
- Where Google Web Risk has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Web Risk?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Web Risk calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Web Risk workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.