> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/operate/overview.md).

# Overview

Keep every customer's integrations working: what needs attention, who is connected, and every run, in one place.

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-73f6df8e27fae97c5e5afd2734852e2da4d5f4af%2Ffastn-lifecycle-5-monitor.svg?alt=media" alt="Stage 5, Run and monitor: support and ops check Health while fastn retries and maintains"><figcaption><p>Where Operate fits in the integration lifecycle</p></figcaption></figure>

## What does it do?

Operate shows how every customer's integrations are doing once they are live. **Health** lists what needs a person today, with the action that fixes it. **Customers** and **Connections** show who is connected to what. **Activity** holds every event and run, down to the individual call. fastn retries, renews tokens and handles rate limits on its own, and its maintainer agent proposes fixes when a vendor changes an API.

## Who is it for?

| Role                             | What they use Operate for                                    |
| -------------------------------- | ------------------------------------------------------------ |
| **Support and customer success** | See which customers need attention before they open a ticket |
| **On-call engineer**             | Find the failed run, read why it failed, and replay it       |
| **Integration engineer**         | Accept the fix when a vendor changes an API                  |
| **Account owner**                | Keep an eye on totals and trends across every customer       |

## How do I use it?

{% tabs %}
{% tab title="Dashboard" %}
Start each day on **Operate → Health**. If **Needs attention** is empty, everything is working. Otherwise each row carries its fix: review a proposed update, ask a customer to reconnect, or open the failed runs.

[Health](https://docs.fastn.ai/operate/health.md) · [Alerts](https://docs.fastn.ai/operate/health/alerts.md) · [Activity](https://docs.fastn.ai/operate/operate.md)
{% endtab %}

{% tab title="Your AI tool" %}
With fastn connected to your AI tool, ask about runs and failures in plain words.

[Connect your AI tool](https://docs.fastn.ai/build/building-from-your-ai-agent/mcp-gateway.md)
{% endtab %}
{% endtabs %}

## Example prompts

| Job           | Prompt                                                                       |
| ------------- | ---------------------------------------------------------------------------- |
| Morning check | *Which workflows failed today, and why?*                                     |
| One customer  | *Show Acme's connections and their last sync.*                               |
| Debug a run   | *Find the failed runs of the order sync this week and summarize the errors.* |
| Stay ahead    | *Which customer connections have expired?*                                   |

## Where things are

| Screen                                                              | Use it to                                                                    |
| ------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| [Health](https://docs.fastn.ai/operate/health.md)                   | See what needs attention, totals and trends, pending vendor fixes and alerts |
| [Customers](https://docs.fastn.ai/operate/customers.md)             | Find a customer and everything they have connected                           |
| [Connections](https://docs.fastn.ai/operate/connections.md)         | Check each signed-in account and its status                                  |
| [Activity](https://docs.fastn.ai/operate/operate.md)                | Read every event, execution and sync report                                  |
| [Troubleshooting](https://docs.fastn.ai/operate/troubleshooting.md) | Match a symptom to its cause and fix                                         |

## Questions?

* Your customers see their own health in the widget: [View sync status and history](https://docs.fastn.ai/for-your-customers/end-user/viewing-sync-status-and-history.md).
* Error meanings: [Errors and failure states](https://docs.fastn.ai/reference/errors.md).

## Works with

* [Build](https://docs.fastn.ai/build/build.md): change a workflow when a failure needs a fix.
* [Embed](https://docs.fastn.ai/embed/embed.md): what your customers see and can fix themselves.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fastn.ai/operate/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
