> 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/embed/widget-builder/features.md).
# Features
The Features tab: optional capabilities your customers get inside the widget.
The live preview keeps rendering the customer's view while you flip these.
Optional capabilities your customers get inside the widget.
**Available now**: both off by default.
| Feature | What it does |
| ---------------------- | ------------------------------------------------------------------------------------ |
| **Catalog connectors** | Shows all catalog connectors in the widget so end users can browse and connect them. |
| **Workflow Diagram** | Shows the generated flow diagram on a workflow inside the widget. |
**Coming soon**
| Feature | What it will do |
| --------------------- | --------------------------------------------------- |
| **Widget filter** | Let end users filter widgets by category or status. |
| **Role based access** | Role-based access control per widget. |
{% hint style="warning" %}
**Catalog connectors** widens the offer from the integrations you curated to everything public in your catalogue. Useful for self-serve products, too broad for most. Decide deliberately.
{% endhint %}
---
# 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/embed/widget-builder/features.md?ask=&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.
