---
title: Workflows
sidebar_label: Workflows
toc_max_heading_level: 3
doc_id: 94213bd6-05bb-4420-8f6f-ddbfdf41758f
description: >-
  Build automations that connect nullplatform features and external tools:
  scheduled scans, action item lifecycles, AI analysis, and integrations,
  without writing and hosting your own services.
keywords:
  - workflows
  - automation
  - triggers
  - action items
  - integrations
  - AI ops
  - nullplatform
---

import LearningPath, { LearningPathRow } from '@site/src/components/LearningPath';
import WorkflowCanvas from '@site/src/components/WorkflowCanvas';
import amiDriftScanner from '@site/src/components/WorkflowCanvas/examples/ami-drift-scanner';
import amiDriftEnsure from '@site/src/components/WorkflowCanvas/examples/ami-drift-ensure';
import amiDriftCloser from '@site/src/components/WorkflowCanvas/examples/ami-drift-closer';

# Workflows <span className="heading-release-pill">New</span>

:::info 🚀 Early release

Workflows is in early release and may not be available in your organization yet. If you'd like to try it or want to know more, [reach out to us](https://docs.nullplatform.com/docs/support) and we'll get you set up.

:::

## What workflows solve

A workflow connects the pieces nullplatform already gives you (action items, the data lake, notifications, agents, approvals) with each other and with your own tools. You describe the automation, refine it visually, and activate it: nullplatform runs it on a schedule, on a platform event, on demand, or whenever one of your own systems posts to the webhook that activation creates for it, with logs for every run.

That makes automation practical for recurring tasks that would otherwise live in spreadsheets and reminders. AMI rollouts or right-sizing become suites that detect the problem, open an action item for the right team, verify the fix, and close themselves.

:::tip 📦 Looking for the source?
The suites you'll find across these docs are working automations you can import and tune, not fixed templates. All of them are open source in [nullplatform/workflows](https://github.com/nullplatform/workflows), along with suites the docs haven't covered yet.
:::

## What a workflow looks like

A canvas of connected steps. Each step is a node: query the data lake, call an API, run code, send a Slack message, or hand a task to AI. Triggers decide when it starts, and every run shows what went in and out of each step.

This is a real suite, the AMI drift tracker from the learning path below. Switch between its three workflows and click any node to see exactly what it runs:

<WorkflowCanvas
  workflows={[
    {id: 'scanner', label: 'AMI Drift Scanner', workflow: amiDriftScanner},
    {id: 'ensure', label: 'Ensure Action Item', workflow: amiDriftEnsure},
    {id: 'closer', label: 'AMI Drift Closer', workflow: amiDriftCloser},
  ]}
  folderLabel="ami-drift"
  height={480}
/>


## Learning path

<LearningPathRow>
  <LearningPath
    title="From hello world to a working AI ops suite"
    steps={[
      {
        label: "Your first workflow",
        href: "/docs/workflows/getting-started",
        note: "Describe a hello world to your coding assistant, run it, activate it. The full loop in minutes.",
        time: "10 min",
      },
      {
        label: "Roll out AMI updates",
        href: "/docs/tutorials/ami-drift",
        note: "The simplest scan-and-track suite, and the best first import.",
        time: "25 min",
      },
      {
        label: "Migrate deprecated Lambda runtimes",
        href: "/docs/tutorials/lambda-runtime-lifecycle",
        note: "An AI step reads the AWS docs and keeps a runtime catalog in your metadata.",
        time: "20 min",
      },
      {
        label: "Right-size Kubernetes costs",
        href: "/docs/tutorials/cost-optimization",
        note: "Price every scope daily and turn real waste into one-click savings.",
        time: "30 min",
      },
    ]}
  />
</LearningPathRow>

:::tip Keep exploring
- [Tutorials](/docs/workflows/tutorials/) index every suite, including the open source ones without a walkthrough yet.
- [Building blocks](/docs/workflows/building-blocks/) covers triggers, nodes, expressions, and secrets: the pieces every workflow reuses.
:::