Write Time Series

cloud_monitoring.write_time_series
ActionGoogle Cloudconnection required

Calls POST /projects/{project}/timeSeries with a custom.googleapis.com metric.

Write one point of a custom metric to Cloud Monitoring.

Connection

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

Configuration

7 fields, 2 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———
metric
Metric name (custom.googleapis.com/{metric}).
stringYes———
value
Point value; the call is refused without it.
numberYes———
value_type
Value type — Cloud Monitoring accepts only the listed values.
stringNodoubleone of "double", "int"—
metric_labels
Metric labels (JSON object).
objectNo———
resource_type
Monitored resource type.
stringNoglobal——
resource_labels
Extra resource labels (JSON object).
objectNo———

Example configuration

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

{
  "resource_type": "global",
  "value_type": "double"
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
metric_type
string—
value
number—
written
number—
{
  "metric_type": "",
  "ok": false,
  "value": 0,
  "written": 0
}

See Write Time Series run in a workflow.

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