Trigger Other

Triggers when the Situation Monitor classifies a matching market signal (news, on-chain event, technical breakout, macro, earnings, M&A, hack/exploit, etc.). Optionally filter by tickers, event types, minimum absolute impact (0-10, default 4), confidence tier (high|medium|low, default high), or scope (asset|sector|market). Powered by services/workers/situation-monitor.

At a Glance

FieldValue
Trigger IDsituation-fired
CategoryOther
Tagsmarket, news, situation-monitor, webhook, alerts

Trigger Configuration

FieldTypeRequiredDescription
tickersarrayNoFilter by ticker symbols (e.g. ['NVDA', 'BTC']). Case-insensitive. Empty/omitted = match any ticker.
eventTypesarrayNoWhitelist of situation event types. Omitted = all event types pass (subject to excludeEventTypes).
excludeEventTypesarrayNoBlacklist of event types. Defaults to ['social_sentiment'] when omitted. Explicit empty array clears the default.
minAbsImpactnumberNoMinimum absolute impact score (0-10). Both bullish +X and bearish -X events pass when |impact| >= this threshold.
confidenceTierstringNoMinimum confidence tier. Inbound situations at or above this rank fire (high > medium > low).
scopestringNoOptionally restrict to a single scope. Omitted = all scopes pass.

Trigger Result

FieldTypeRequiredDescription
triggeredAtstringYesTimestamp when the situation was received (UTC, RFC3339 format)
situationobjectYes-
tickersarrayYesTickers this situation references

Workflow Root Example

json
{ "nodes": { "root": { "type": "situation-fired", "payload": { "tickers": [], "eventTypes": [], "excludeEventTypes": [], "minAbsImpact": 4, "confidenceTier": "high" }, "children": [ "log_event" ] }, "log_event": { "type": "log", "payload": { "message": "Triggered at {{$trigger.triggeredAt}}" }, "children": [] } }}

Downstream nodes can use {{$trigger.triggeredAt}} and any result fields listed above. Event triggers usually expose the raw source payload under a field such as event, body, trade, or raw.