Trigger the Operator agent from external systems: CI events, form submissions, data updates, and monitoring alerts.
Webhooks let external systems trigger the Operator agent. Use them to feed new data to agents, kick off scoring when outcomes resolve, or start actions when something happens outside Operator.
When new inputs arrive (a batch of transactions, fresh sensor readings, new labeled data), a webhook sends them to the Operator agent, which routes them to the right instance.
New transaction batch arrived for fraud scoring.{{payload}}Run the fraud-detector agent against these transactions and log the predictions.
When outcomes resolve (a chargeback is confirmed, actual AQI is published, a repo actually trends), a webhook delivers the result so the Operator agent can score previous predictions.
Actual AQI readings arrived for yesterday's predictions.{{payload}}Score the aqi-predictor agent's predictions against these actuals.Post the updated accuracy to this thread.
A deployment fails in CI. A monitoring alert fires. A data pipeline completes. The webhook triggers the Operator agent to decide what to do.
A deployment event just arrived.{{payload}}Summarize what changed, decide whether any instance action is needed, and take it.
