Use case examples
These are blueprints — realistic, prompt-driven scenarios that show how to get real work done with Higento. Each example starts from a natural request you'd actually type, frames it as a sensible end-to-end task, and shows the functions Higento chains together to complete it.
Examples are grouped by theme so related scenarios live on one page. Within each page, every blueprint lists:
- Goal — what you're trying to achieve.
- Example prompt — what you say to Higento.
- Functions used — the chain Higento runs.
- What you get — the resulting workspace state.
Higento always discovers ids first (usually with
folder-list), then acts. When it changes an agent, chatbot, or tool, it commits a draft version and asks you to deploy before it goes live.
Themes
| Theme | What it covers | Page |
|---|---|---|
| Workspace organization | Creating, renaming, and reorganizing folders; moving objects between folders. | Workspace organization |
| Building & running agents | Creating agents, attaching tools and integrations, scheduling, and running them. | Building & running agents |
| Chatbots | Creating, reviewing, and refining chatbots. | Chatbots |
| Building tools | Authoring prompt, template, and code tools with input/output interfaces. | Building tools |
| Tables & data | Defining tables, saved views, row CRUD, pagination, filters, and column value counts. | Tables & data |
| Folder dashboards | Enabling folder dashboards and adding KPI/chart widgets backed by tables. | Folder dashboards |
For the underlying function contracts, see the Functions reference.