GoClaw runs workflows on a schedule, when you start them, or when an outside system calls one of its webhooks (GitLab, Graylog, or anything that can send an HTTP POST).
gitlab_hook), with the goclaw gitlab hook wizard, or by hand./goclaw/hook/graylog/<key>) and runs a SOP. Set it up by asking the agent, which registers the alert in Graylog and the route in GoClaw, or by hand: a Graylog route on the Webhooks page and an HTTP notification in Graylog./goclaw/hook/sonarqube/<key>) and a failed quality gate (or every analysis) runs a SOP. Set it up by asking the agent, which makes the webhook in SonarQube and the route in GoClaw, or by hand./goclaw/hook/zabbix/<key>), and each runs a SOP. Set it up by asking the agent, which makes the media type, a user and group of its own and the action in Zabbix and the route in GoClaw, or by hand./goclaw/hook/uptrace/<key>?token=…) when an alert opens, and runs a SOP. Set it up by asking the agent, which makes the monitor and its channel in Uptrace and the route in GoClaw, or by hand./goclaw/hook/wazuh/<key>) with what it found, which runs a SOP. Nothing changes on the manager. Set it up by asking the agent, which makes the monitor and its channel in the indexer and the route in GoClaw, or by hand./goclaw/hook/grafana/<key>) when the rule fires, and runs a SOP. Set it up by asking the agent, which makes the rule, its contact point and the route in GoClaw, or by hand.Any other system that can POST JSON reaches an agent the same way, through a webhook route: see Webhook Routes. A route can run a SOP for each event, or gather a window of events into one run.