---
title: "Workflows — FireFight"
description: "Turn the steps your team repeats into workflows that run on a schedule, on an alert, or with one click, drawn on a canvas or built by asking Halon."
canonical: https://firefight.app/product/workflows
---

# Workflows

**Your runbooks, running themselves**

Turn the steps your team repeats into workflows that run on a schedule, on an alert, or with one click. Draw them on a canvas, or just ask Halon.

[Sign in with Slack](https://app.firefight.app/)

## From a sentence to a workflow you can read

Every workflow is drawn as its steps, so anyone can see what it will do before it runs.

### Make

**Start in seconds.** Pick one from the library, or tell Halon what you want and when. It shows you every step before it builds it.

- Workflow library
- Made from a chat
- Export and import

### Build

**See every step.** Edit on a canvas. Changes stay in a draft until an admin publishes them, so the live version keeps running untouched.

- Visual canvas
- Drafts and versions
- Publish when ready

### Run

**Test it, then trust it.** Try a run safely before going live. Every real run shows what each step did, and you can retry or skip a step that failed.

- Safe test runs
- Every step's result
- Retry or skip

## Every step on one canvas

See what each step reads or changes. Edits stay in a draft until published.

## Triggers, steps and people, all on one canvas

### Starts on its own

On a schedule, an alert, an incident, a deploy or a change on the map.

### Only when it matters

Narrow it to the incidents you care about, and a storm can't start a flood of runs.

### Only the access you give it

A workflow can do only what an admin granted it, and every call is recorded.

### People in the loop

Wait for an approval, ask someone a question, or hand off a task.

### Code when you need it

Run a script or call any public API when the built-in steps aren't enough.

### Every tool you connected

Read status, restart a service, open an issue, anything your integrations can do.

## Documentation

- [Workflows](https://firefight.app/docs/ai/workflows.md): What starts a workflow, what it can do, and who can make one.
- [Building a workflow on the canvas](https://firefight.app/docs/ai/workflow-canvas.md): Build, test and publish a workflow, and follow each run.
- [Workflow library](https://firefight.app/docs/ai/workflow-library.md): Start from a workflow Firefight ships, or bring one from another workspace.
- [Permissions](https://firefight.app/docs/gateway/permissions.md): Decide what each workflow may do.
- [Approvals](https://firefight.app/docs/gateway/approvals.md): Hold a change until someone approves it.
- [Outbound webhooks](https://firefight.app/docs/api/webhooks.md): Send incident events to your own systems.

## Write down how your team responds

Start from the library or ask Halon. Nothing runs until an admin publishes it. [Sign in with Slack](https://app.firefight.app/).