Skip to main content

Product Introduction

Overview​

Workflow Orchestration turns a repeated operations response into a saved workflow. A workflow starts with one trigger, then continues with actions, a condition, and human approval. Triggers are form, schedule, webhook, and NATS. Actions call job execution, HTTP, an OpsPilot agent, intent classification, memory read and write, document rendering, and the notification channels already configured in System Management.

Use it when the path is stable: an alert or a submitted form, a decision, an action on an authorized host or a notification, an approval when a person must decide, and an execution record afterward.

Core Advantages​

  1. Start with a trigger
    A new workflow chooses form, schedule, webhook, or NATS first. A schedule runs on a frequency. A webhook accepts an external call. NATS accepts platform messages such as alerts. A form opens a page, and submitting it starts a run.

  2. Actions reuse capabilities that already exist
    Job execution runs a Linux or Windows script on authorized targets. Notification uses email, WeCom, Feishu, DingTalk, or Webhook from System Management. Agent, intent classification, and memory use OpsPilot resources available to the current organization. Document rendering fills a Word or Excel template and produces a downloadable file.

  3. Conditions and approval stop automation where a person or a rule must decide
    A condition uses structured rules and has only two exits: matched and not matched. It does not accept a free expression. Human approval names candidates. Approval continues the pass path. Rejection requires a reason and takes the rejection path.

  4. Every run has a state and a record
    Home shows recent runs, a trend, and approvals waiting for you. Record states are Queued, Running, Waiting for Approval, Terminating, Outcome unknown, Succeeded, Failed, Timed Out, and Terminated. A test run can be stopped manually.

Use Cases​

  • Start a fixed response from an alert
    Use NATS or a webhook, branch on a condition, then notify the on-call person or run a job that only collects information on an authorized host.

  • Approve a change before it runs
    Collect the change on a form, wait for approval, then run a job or send a notification. Rejection stays on the rejection path.

  • Produce a report on a schedule
    Read memory or call an agent, render a document, and send the file through a notification channel.