Google Threat Intelligence
threatintelligence.googleapis.com API (Google OAuth2).
OCNORA ships 5 typed Google Threat Intelligence 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 Threat Intelligence
- 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 Threat Intelligence
Operations, grouped by what they do to your data.
Read and search 4
Other operations 1
A sample Google Threat Intelligence workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Threat Intelligence trigger is needed.
- 2Get Alertthreat_intelligence.get_alertGet an alert by name.
- 3Enumerate Facetsthreat_intelligence.enumerate_facetsEnumerateAlertFacets returns the facets and the number of alerts that meet the filter criteria and have that value for each facet.
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 5
- Enumerate FacetsEnumerateAlertFacets returns the facets and the number of alerts that meet the filter criteria and have that value for each facet.threat_intelligence.enumerate_facets
- Get AlertGet an alert by name.threat_intelligence.get_alert
- Get ConfigurationGet a configuration by name.threat_intelligence.get_configuration
- List AlertsGet a list of alerts that meet the filter criteria.threat_intelligence.list_alerts
- List ConfigurationsGet a list of configurations that meet the filter criteria.threat_intelligence.list_configurations
Google Threat Intelligence questions
- How does OCNORA authenticate with Google Threat Intelligence?
- 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 Threat Intelligence?
- 5 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Threat Intelligence operation I need is not listed?
- Where Google Threat Intelligence 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 Threat Intelligence?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Threat Intelligence 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 Threat Intelligence 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.