Workflow Orchestration
The orchestration engine underneath every StackHeal product. Define what starts a workflow, what it checks, which systems it calls, who has to approve it, and how its result is verified — then watch every run in one place.
Workflow canvas · wf.disk_reclaim.v3
Benefits
Assets, tenants, environments and maintenance windows are first-class concepts, not custom fields you have to model yourself.
Insert a human decision anywhere in a workflow, with the context the approver needs rendered at the moment they are asked.
Steps declare whether they are safe to repeat. Retries resume from the failure instead of replaying side effects.
Every run keeps its inputs, outputs, branch decisions, timings and approvals, so you can answer what ran and why.
How it works
Five building blocks cover the operations work teams automate.
Start a workflow from a webhook, a monitoring alert, a ticket event, a schedule, an API call or a manual run with typed parameters.
Branch on asset attributes, tenant policy, severity, time of day, maintenance state or the output of an earlier step.
Call registered actions: platform APIs, Ansible playbooks, scripts over a managed transport, HTTP requests, or another workflow.
Pause for a named approver or role, with a timeout policy that decides what happens if nobody responds.
Assert the expected end state, then record the outcome. A run that cannot verify itself is reported as unverified, not successful.
Example workflows
Composite workflows that cross system boundaries — the ones that currently live in someone's head.
Trigger: Service desk ticket matching a known intent
Trigger: Signed order in your billing or CRM system
Trigger: Monthly schedule
Trigger: Quarterly schedule or manual run
About these examples
Compatibility
Systems connect through maintained connectors or through their own APIs and webhooks. Check the directory for each system's current status.
Controls
An orchestration engine is only as safe as the boundary around its actions.
Workflows compose from an action catalogue you control. Authors cannot introduce arbitrary new capabilities inside a workflow body.
Separate who may write a workflow, who may publish it, and who may run it against which environments.
Credentials are referenced by name and resolved at execution time from a secret store. They are never stored in workflow definitions.
Workflows are versioned, diffable and revertible, and each run records the version that executed.
StackHeal products share one workflow engine, one action catalogue and one run history.
Turn incoming support requests into structured, actionable workflows.
Learn moreStandardize virtual machine provisioning and infrastructure lifecycle operations.
Learn moreCoordinate backup jobs, monitor outcomes, and simplify recovery procedures.
Learn moreThe questions we are asked most often in evaluation calls.
Something not covered here? Ask our team.
We will scope a proof of concept around one or two of the request types your team handles most often, and show you what the run history looks like.