List Alerts

threat_intelligence.list_alerts
ActionGoogle Cloudconnection required

Calls Threat Intelligence GET /v1beta/projects/{projectsId}/alerts.

Get a list of alerts that meet the filter criteria.

Connection

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

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
filter
Optional. Filter criteria. Supported fields for filtering include: * `audit.create_time` * `audit.creator` * `
stringNo———
order_by
Optional. Order by criteria in the csv format: "field1, field2 desc" or "field1, field2" or "field1 asc, field
stringNo———
page_size
Optional. Page size. Default to 100 alerts per page. Maximum is 1000 alerts per page.
numberNo50≥ 1—
page_token
Optional. Page token to retrieve the next page of results.
stringNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "page_size": 50
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
alerts
array—
nextPageToken
string—
{
  "alerts": [],
  "nextPageToken": "",
  "ok": false
}

See List Alerts run in a workflow.

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