Actions13
- Assistant Actions
- Chat Actions
- Document Actions
- File Actions
- Metric Actions
- Model Actions
- Transcript Actions
Metric → Record Observation
AI-generatedSummary
Records one numeric observation for a Petals metric, creating or updating its definition from the supplied metric details. The node sends the reading and definition to Petals for each input item.
Inputs
- Slug (required) — Stable lowercase snake_case identifier for the metric, such as body_weight.
- Label (required) — Human-readable metric name.
- Description (required) — What the metric captures.
- Unit (required) — Measurement unit, such as kg or bpm.
- Aggregation Hint — How values aggregate over a window: average (default), maximum, minimum, or sum.
- Value (required) — Numeric reading to record.
- Occurred At (required) — ISO 8601 timestamp for when the reading occurred; valid dates are sent in UTC.
- Additional Fields: Note — Optional short note attached to the observation.
- Additional Fields: Valid Range Max — Optional upper bound included in the metric definition for sanity validation.
- Additional Fields: Valid Range Min — Optional lower bound included in the metric definition for sanity validation.
Output shape
One item per response row, containing the Petals API response as JSON.
The operation sends a POST request to record the metric definition and observation. If the API returns an array, each element becomes a separate output item; otherwise the response is returned as one item. With Continue On Fail enabled, errors are returned as items with an error field.