---
name: nova-flow-monitor
description: Check how Nova Flow automations are performing and find out why one did not do what was expected. Use when someone asks what their automations did, why a run failed, whether an account is healthy, or how many credits are left, and the Nova Flow MCP server is connected.
---

# Checking on Nova Flow

Use the Nova Flow MCP server, and only report what it returns.

## Starting point

Call `whoami` first to see the workspace and what this connection can reach. Some parts (contacts, credits, comment policies, support) may be switched off for the role or the workspace; if so, say that rather than skipping silently.

## Questions and the tools that answer them

- **What is running?** `list_automations`, then `get_automation` for the one in question.
- **What did it do?** `list_runs` filtered by automation and status, newest first.
- **Why did that run fail or stop?** `get_run` shows each step and how it ended. Read the step that failed and its error before guessing.
- **Is the account connected and healthy?** `list_accounts`: status, when the token expires, whether it is rate limited.
- **Who has been talking to us?** `list_contacts`, by tag or by name.
- **Are we running out?** `get_credits`: the monthly grant and bought credits are separate buckets.
- **What did the moderation policy hide?** `list_comment_reviews`.

## Reporting back

Lead with the answer. Then the evidence: which runs, which step, what the error said. Separate what you saw from what you suspect, and say which is which. If something needs a change in the dashboard (reconnecting an account, buying credits), say exactly where.

Do not invent numbers, and do not describe runs you have not read.
