> ## Documentation Index
> Fetch the complete documentation index at: https://docs.costgraph.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows

> Give CostGraph a goal, and approve each change it proposes before it happens

A workflow turns a finding into a change. You describe a goal, such as "turn
down idle GPU node pools in production", and the CostGraph agent works toward
it. The agent reads your cost data, inspects the resources it involves, and
proposes the changes that meet the goal.

The agent doesn't change anything on its own. Each change waits for an admin or
organization owner to approve it. CostGraph then applies that exact change
once, checks that it took effect, and records the result on the run.

Workflows is in beta. Open it from **Workflows** in the CostGraph sidebar.

## Goals, runs, and approvals

* **Goal**: what the agent works on, the tools it can use, what it may change,
  and when it runs. A goal runs once or on a schedule.
* **Run**: one attempt at a goal. The run page shows what the agent read, its
  plan, each step, and the outcome.
* **Approval**: a pause in a run where the agent shows you one change and waits
  for you to approve or reject it.

## Why every change needs approval

The agent writes its own plan, so a person checks each change before it
happens. An approval shows the exact change: the resource, the current value
and the new one, the estimated impact, and the risk. Your approval covers that
change and nothing else.

Deletes and other changes that can't be undone always wait for approval. For
the details, see [Approvals](/costgraph/workflows/approvals).

## Roles

Anyone in the tenant can view goals, runs, and pending approvals. Managing them
needs a higher role. The following table lists who can do what:

| Action | Who can do it |
| - | - |
| View goals, runs, and approvals | Any member of the tenant |
| Create, edit, pause, or delete a goal | Admins and organization owners |
| Run a goal now, retry, cancel, or message a run | Admins and organization owners |
| Approve or reject a change, or answer a question | Admins and organization owners |
| Start a workflow from Graph AI | Admins and organization owners |

A workflow's changes run as the person who created the goal, with that
person's access. If they leave the organization, or lose the role a change
needs, the change fails and nothing is changed.

## Workflows pages

The **Workflows** area has three tabs and a **New goal** button:

* **Overview**: your goals, their latest runs, anything waiting for you, and
  estimated monthly savings from approved changes still in place.
* **Runs**: every run, with search and filters for goal, status, and trigger.
* **Connected tools**: the outside tools the agent can use, and the goals that
  use each one.

## Connected tools

Without a connected tool, the agent reads CostGraph data and changes only
CostGraph records, such as budgets and reports. To let it work in other
systems, connect them from **Integrations**:

* **AWS**: turn on **Let Workflows make approved changes** when you connect
  the account. This adds a separate automation role that Workflows uses only
  for changes your goals allow.
* **GitHub**: install the CostGraph GitHub App to let workflows open pull
  requests and GitHub issues.
* **Jira** and **Linear**: connect them to let workflows file tickets. See
  [Jira](/costgraph/integrations/jira) and
  [Linear](/costgraph/integrations/linear).

## Next steps

<CardGroup cols={2}>
  <Card title="Goals and runs" icon="bullseye" href="/costgraph/workflows/goals-and-runs">
    Create a goal and follow its runs.
  </Card>

  <Card title="Approvals" icon="circle-check" href="/costgraph/workflows/approvals">
    Review, approve, or reject a change.
  </Card>

  <Card title="What workflows can change" icon="list-check" href="/costgraph/workflows/what-workflows-can-change">
    Every change a workflow can make.
  </Card>

  <Card title="Workflows from Graph AI" icon="comments" href="/costgraph/workflows/graphai">
    Start a workflow from chat, Slack, or MCP.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.