---
title: "Workflows"
description: "Configure beta workflows that automate company tasks."
icon: "route"
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

<Note>Workflows are in **beta**.</Note>

The **Workflows** area lets you compose platform primitives into executable company tasks. A
workflow combines a trigger with one or more steps, then runs automatically whenever the trigger
fires.

After you configure a workflow, it becomes a durable executable version of that task. Each run
captures performance data, and agents in the workflow are automatically improved when feedback
signals are available.

## Configuration

### Trigger

Choose the event that starts the workflow.

| Trigger | Use it to |
|---------|-----------|
| Monitor alert | Start a workflow when a monitor alert trips |
| New hardware data event | Start a workflow when a Thing reports new data |
| New ingress integration event | Start a workflow when an inbound integration produces an event |
| Schedule | Start a workflow on a recurring time-based schedule |

### Steps

Add steps in the order the task should run. Steps are composable and can pass context forward to
later steps.

| Step type | Use it to |
|-----------|-----------|
| Data query | Read platform data, including telemetry, aggregates, latest values, and related context |
| Thing command | Send an action to connected hardware |
| Egress integration command | Send data or notifications to an outbound integration |
| Agent | Run a forecasting, anomaly detection, integration, or other specialized agent |

## Executions

Each workflow execution records what triggered the run, which steps ran, their outcomes, and the
available performance data. Use execution history to understand whether the workflow completed,
where it spent time, and which step produced the result.

If an execution includes an agent and a feedback signal is available, the platform uses that
signal to improve the agent automatically.

## Common patterns

- **Alert response:** a monitor alert triggers a workflow that queries recent data, runs an
  anomaly detection agent, and notifies an operator.
- **Hardware action:** a new hardware data event triggers a workflow that evaluates current
  state and sends a Thing command.
- **Integration handoff:** a new ingress integration event triggers a workflow that runs an
  integration agent and sends the result to an egress integration.
- **Scheduled planning:** a schedule triggers a forecasting agent and pushes the forecast to a
  downstream system.

## Related docs

- [Monitors](/console/monitors) can trigger workflows from alerts.
- [Integrations](/console/integrations) can produce ingress events or receive egress commands.