> 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.md).

# Operate

- [Activity](https://docs.fastn.ai/operate/operate.md): Watching what actually happens once integrations are live.
- [Events](https://docs.fastn.ai/operate/events.md): Everything moving in and out of your customers' systems, newest first.
- [Traces](https://docs.fastn.ai/operate/traces.md): Every workflow run that called a connected system.
- [Alerts](https://docs.fastn.ai/operate/alerts.md): Get told when something crosses a line you care about. Checked every 15 minutes.
- [Executions](https://docs.fastn.ai/operate/executions.md): Every workflow run, newest first.
- [Triggers](https://docs.fastn.ai/operate/triggers.md): Firing the triggers you have built, from your own systems.
- [Using a webhook trigger](https://docs.fastn.ai/operate/triggers/using-a-webhook-trigger.md): Call a webhook trigger from your backend once it exists, with an example curl.
- [Sync reports](https://docs.fastn.ai/operate/sync-reports.md): What changed on the last run of each sync, record by record.
- [Customers](https://docs.fastn.ai/operate/customers.md): Every customer using your embedded integrations.
- [Troubleshooting](https://docs.fastn.ai/operate/troubleshooting.md): Symptom, where to look, and what usually fixes it.


---

# 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.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.