From request to run
- 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.
- Graph AI checks that you want it to go ahead.
- 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.
- The workflow plans the change and waits for approval on the run page.
- After approval, CostGraph applies the change, reads the record again to confirm it took effect, and records the result.
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.
From MCP
A coding agent connected over MCP uses two tools:startWorkflowRunstarts a run and returns its id and link.getWorkflowRunreads a run’s status, summary, and steps, with links to the tickets, reports, or pull requests it created, and whether it waits for approval.
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 withgetWorkflowRun 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.Next steps
Approvals
Review, approve, or reject a change.
AI and your data
What Graph AI sends to its model and what CostGraph stores.