Run Lifecycle and StatusesEvery execution of an automation is a run — a durable record you can inspect in the run history of the automation. This page explains what each status means, how a run moves through its lifecycle,…
Triggers and execution guarantees (reference)Automations start in one of three ways — on demand, on a schedule, or via webhook — plus two special paths (runs started by StackJack staff, and runs invoked by a connected AI assistant). This page…
Webhook ingestion contract (reference)Webhook-triggered automations expose a unique, public HTTPS endpoint that external systems (your PSA, RMM, alerting stack, Zapier, and so on) POST to. This page is the full contract for anyone…
Guardrails and Safety ControlsEvery automation runs inside a layered set of safety controls. This page describes each guardrail, what it protects against, and exactly how it behaves — so you can reason about what an automation can…

Support