Back to Blog

Introducing Workflow Engine v2 for modern teams at scale

Chris Parker

Product Lead at AlteraOS

March 8, 2026

Workflow Engine v2 is now available. This update improves how workflows are built, reviewed, and operated across teams. The goal is clearer logic, safer execution, and better visibility when automation scales.

What changed

The first version proved the foundation. Teams automated handoffs, reduced manual coordination, and kept execution moving without constant check ins.

As adoption grew, the same issues appeared in different environments. Workflows were hard to review quickly. Changes felt risky because intent was not always obvious. Debugging required too much guesswork.

Workflow Engine v2 focuses on two priorities: readability and operational control.

Clearer workflow structure

Workflows now read like a sequence you can scan quickly. Triggers, conditions, and actions are grouped to make intent obvious.

A workflow reads like a plan

Instead of a long list of disconnected steps, v2 presents a flow that mirrors how teams think about process. This matters when multiple people maintain automation together. It also matters months later when the original author is not the person making updates.

Conditions became explicit

Conditions are easier to see and reason about. This reduces accidental logic that looks correct but behaves differently in production.

Example rule shape:

const workflowRule = {
  trigger: "issue.status_changed",
  when: {
    to: ["In Progress", "Review"],
    priority: ["High"],
  },
  then: [
    { action: "assign.reviewer", team: "Core Engineering" },
    { action: "notify.channel", channel: "eng-triage" },
  ],
};

const workflowRule = {
  trigger: "issue.status_changed",
  when: {
    to: ["In Progress", "Review"],
    priority: ["High"],
  },
  then: [
    { action: "assign.reviewer", team: "Core Engineering" },
    { action: "notify.channel", channel: "eng-triage" },
  ],
};

const workflowRule = {
  trigger: "issue.status_changed",
  when: {
    to: ["In Progress", "Review"],
    priority: ["High"],
  },
  then: [
    { action: "assign.reviewer", team: "Core Engineering" },
    { action: "notify.channel", channel: "eng-triage" },
  ],
};

This shows the intent of v2. A trigger defines the event. The condition describes when the rule applies. Actions describe what happens next.

More context during execution

v2 evaluates state with more context. Rules can consider who owns the work, where it sits in the process, and the metadata teams rely on.

Fewer false positives

A common problem in automation is a rule that fires when it should not. Better context helps rules behave predictably without multiplying complexity.

Better handoffs

Teams often want different behavior for different stages. With richer context, workflows can reflect real handoffs without becoming hard to maintain.

Safer controls for operators

Automation is only useful if teams trust it. v2 includes guardrails for testing, observability, and control.

Test mode

Test mode lets teams validate a workflow before it impacts real work.

import { altera } from "@alteraos/sdk";

const client = altera({ apiKey: process.env.ALTERA_API_KEY });

const result = await client.workflows.test({
  workflowId: "wf_128",
  payload: {
    event: "issue.status_changed",
    data: { status: "Review", priority: "High" },
  },
});

console.log(result.preview);

import { altera } from "@alteraos/sdk";

const client = altera({ apiKey: process.env.ALTERA_API_KEY });

const result = await client.workflows.test({
  workflowId: "wf_128",
  payload: {
    event: "issue.status_changed",
    data: { status: "Review", priority: "High" },
  },
});

console.log(result.preview);

import { altera } from "@alteraos/sdk";

const client = altera({ apiKey: process.env.ALTERA_API_KEY });

const result = await client.workflows.test({
  workflowId: "wf_128",
  payload: {
    event: "issue.status_changed",
    data: { status: "Review", priority: "High" },
  },
});

console.log(result.preview);