> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/app-builder/app-builder-app-examples-and-prompts.md). # App Builder: App examples and prompts Below are 10 examples of common uses for creating an app with Rewst's App Builder, complete with the prompts we recommend you feed RoboRewsty to help you create them. The common thread across all is that App Builder lets you put a professional, controlled front end on top of your Rewst automation, solving the problem of getting data and actions into the hands of people who shouldn't need to touch the platform directly. ## **1. Replace expensive third-party client portals** Instead of paying for a separate client-facing portal tool, you can build a fully branded, white-labeled portal hosted on your own subdomain. MSPs have used this to replace standalone software entirely, with role-based access, forms, and direct workflow triggers all in one place. {% hint style="info" %} Prompt: "Build me an App Builder app that serves as a white-labeled client portal. It should have a landing page with role-based navigation links, embedded forms, and buttons that trigger workflows. What pages and components do I need?" {% endhint %} ## **2. Self-service end user portal** Give your clients' end users 24/7 access to common automations — password resets, account unlocks, group membership changes, employee onboarding/offboarding — without ever calling the service desk. This directly reduces ticket volume for repetitive, low-complexity requests. {% hint style="info" %} Prompt: "What does the End User Portal prebuilt app include, and what Crates do I need installed before requesting it? Walk me through the prerequisites." {% endhint %} ## **3. Centralized forms hub** Rather than sending users to scattered Rewst form links, build a Forms Portal that aggregates all the forms a user has permission to see, with search and filtering built in. This makes it easy for clients or internal staff to find and submit the right request every time. {% hint style="info" %} Prompt: "What does the Forms Portal prebuilt app do and how do I request it? What permissions model does it use to control which forms each user sees?" {% endhint %} ## **4. Operational analytics and reporting dashboard** Surface PSA data, device health metrics, and workflow execution trends in a clean, readable dashboard. Instead of exporting reports manually or relying on your PSA's limited reporting, you can build a live view that pulls directly from your Rewst workflows and integrations. {% hint style="info" %} Prompt: "Help me design an App Builder page that displays a data table and charts pulling from a Rewst workflow output. What components should I use and how do I connect them to workflow data?" {% endhint %} ## **5. Technician toolbox internal ops dashboard** Build an internal-facing app for your own team, a single location where technicians can trigger common automations, check workflow statuses, manage triggers, or run bulk operations without needing to navigate the full Rewst platform. {% hint style="info" %} Prompt: "I want to build an internal App Builder app for my technicians. It should let them trigger common workflows via buttons and see recent execution statuses. What's the best way to structure this with App Builder components and workflow inputs?" {% endhint %} ## **6. White-labeled branded experience for clients** App Builder supports custom logos, color palettes, typography, and custom subdomains. This means every client can see an app that looks like your brand, not a generic tool, a major differentiator when selling managed services. {% hint style="info" %} Prompt: "Walk me through setting up custom branding in App Builder — logo, colors, typography, and a custom subdomain. What's the recommended approach for applying branding consistently across multiple apps?" {% endhint %} ## **7. Ticket submission and status tracking** Build a lightweight ticketing intake app where end users can log requests and then track the status of their submitted tickets, all connected to your PSA via Rewst workflows. There's no need for a full-blown ITSM portal license. {% hint style="info" %} Prompt: "Help me build an App Builder page where end users can submit a support ticket via a form and then view the status of their previously submitted tickets. What workflow and component setup do I need?" {% endhint %} ## **8. Employee onboarding and offboarding self-service** HR or managers at a client site can trigger onboarding or offboarding workflows directly from a clean web interface, filling in the relevant details via a form. The App Builder front end handles the UX while Rewst handles all the back-end provisioning logic. {% hint style="info" %} Prompt: "I want to build an App Builder form page that lets a manager trigger an employee onboarding or offboarding workflow by filling in user details. What components and workflow trigger setup should I use?" {% endhint %} ## **9. Workflow trigger management dashboard** Build an app that lets authorized users manage and fire specific automation triggers on demand, without giving them access to Rewst itself. This is useful for scheduled tasks, bulk operations, or anything that needs a human "go" button. {% hint style="info" %} Prompt: "Help me build an App Builder page that lists available automation triggers and lets authorized users fire them on demand. How do I connect a button component to a specific workflow trigger?" {% endhint %} ## **10. Custom reporting portals per client** Rather than one-size-fits-all reporting, you can build per-client dashboards that surface only the data relevant to that organization: device counts, ticket trends, automation savings, SLA metrics. All are dynamically pulled from your workflows and presented in a polished, client-ready format. {% hint style="info" %} Prompt: "I want to build a reporting app in App Builder that shows a different client's data depending on who is logged in. How do I use authentication and org context to dynamically filter the data shown on the page?" {% 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.rewst.help/documentation/app-builder/app-builder-app-examples-and-prompts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.