Workflows and Watchers

Define repeatable agent work with cron triggers, data-change triggers, and metric watchers.

Workflow shape

A workflow definition stores the goal, system prompt overlay, steps, enabled state, owner, daily run budget, output contract, and optional trigger configuration. Workflow definitions are also best-effort serialized into config version control as markdown.

Field	Meaning
goal	The durable purpose of the workflow
steps	Ordered instructions the agent should follow
cron / cron_timezone	Scheduled execution settings
daily_run_budget	A guardrail on repeated runs
output_contract	Expected output shape for downstream review

Trigger types

Trigger	Use it for	Important fields
cron	Scheduled recurring work	cron, cron_timezone, cron_enabled
when	Data-change driven runs	table, where, select, primary_key, version_column, idempotency_key_template
subscription	Source observations and fan-out controlled by subscription settings	max_concurrent_runs, debounce, dedupe and source write accounting
watch	Metric thresholds and change detection	query, value_path, op, threshold, cadence_seconds, debounce_seconds
manual	Operator-triggered runs from the UI or control plane	thread_id, trigger payload, and actor context

Watchers

Watchers run GraphJin queries on a cadence, extract a dotted value path, compare the result, and enqueue a workflow fire when the condition is met. Cadence is clamped to at least 60 seconds, and debounce defaults to 3600 seconds.

Operator	Meaning
gt	Value is greater than the threshold
gte	Value is greater than or equal to the threshold
lt	Value is less than the threshold
lte	Value is less than or equal to the threshold
eq	Value equals the threshold
ne	Value does not equal the threshold
changed	Value differs from the last observed value