> ## 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 from Graph AI

> Ask Graph AI to make a change from chat, Slack, or MCP, and approve it on the workflow run page

Graph AI answers questions about your spend, and it can also act on them.
Ask it for a change, such as "open a Jira ticket for this anomaly", and it
hands the work to a workflow. The workflow makes the
change after an admin or organization owner approves it on the run page.

This works the same way in the CostGraph app's Graph AI chat, in
[Slack](/costgraph/slack/overview), and from a coding agent connected over
[MCP](/costgraph/mcp/install).

## From request to run

1. You ask Graph AI for a change. It reads what the change involves first,
   such as the budget or report you named, so the workflow knows the exact
   record and its current state.
2. Graph AI checks that you want it to go ahead.
3. It starts a workflow run with a name and a description of the work,
   including the records, ids, and numbers it found. The run starts right away
   and runs once.
4. The workflow plans the change and waits for approval on the run page.
5. After approval, CostGraph applies the change, reads the record again to
   confirm it took effect, and records the result.

A run Graph AI starts always asks before every change. It can make any change
on [What workflows can change](/costgraph/workflows/what-workflows-can-change)
that your connected tools support. The run appears under **Workflows** like
any other, with its own goal.

## In the app

In Graph AI chat, the run shows as a card with its name, status, and live
steps. When a change waits for approval, click **Review and approve** to open
the run page. Click **View run** to follow it at any time.

## In Slack

Graph AI shares the run link in the thread, then follows the run there:

* When a step finishes, with its summary and any links, such as a ticket or a
  pull request.
* When the run waits for someone to approve a change, with a link to review
  it.
* When the run finishes, with its summary.

Approve changes on the run page in CostGraph, not in Slack. If a run goes on
for a long time, Graph AI stops following it and posts a link to the run.

## From MCP

A coding agent connected over MCP uses two tools:

* `startWorkflowRun` starts a run and returns its id and link.
* `getWorkflowRun` reads a run's status, summary, and steps, with links to the
  tickets, reports, or pull requests it created, and whether it waits for
  approval.

Your agent can call `getWorkflowRun` again to check on the run. Share the run
link with an admin or organization owner to approve the change.

## Roles

Only admins and organization owners can start a workflow from Graph AI. For
anyone else, Graph AI changes nothing and replies with a link to **New goal**
in CostGraph, so an admin can set up the work.

Reading a run with `getWorkflowRun` works for any member of the tenant.

## Billing

On Slack and MCP, Graph AI needs active billing on your tenant, and its
requests are billed as AI assistant requests. See [Billing](/costgraph/billing).

## Next steps

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

  <Card title="AI and your data" icon="shield" href="/costgraph/slack/ai-and-data">
    What Graph AI sends to its model and what CostGraph stores.
  </Card>
</CardGroup>


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