> 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/rewst-documentation/documentation/rewst-agent/rewst-agent-capabilities.md). # Rewst Agent capabilities ## What can the Rewst Agent build? Ask the Rewst Agent to build you anything that you could have built in Rewst before— only now, it will take the lead and do all the work for you. For anything the Rewst Agent builds, it will research, show a proposal with the exact nodes and field mappings, then ask once for approval. If its proposal is off, just tell it what to change, and it will make adjustments and ask for approval again. Note that whatever permissions and roles you have in Rewst dictate the things the Rewst Agent can do for you. If you don't have permissions to build workflows, for example, the Rewst Agent also won't be able to build workflows. Learn more about settings in Rewst [here](/rewst-documentation/documentation/settings.md). #### Workflows Workflows are the core of Rewst automation, multi-step processes that connect triggers, logic, and actions. * Build workflows from scratch, including triggers, loops, branching logic, data transforms, and integration actions * Edit and update existing workflows: add nodes, rewire logic, or fix configurations * Publish and run workflows, then inspect the results to confirm that they worked * Debug failures by tracing run steps and pinpointing where things broke * Integrate with external systems: PSA/RMM tools, Microsoft 365, and other connectors you have installed in Rewst
#### Forms * Build forms and workflow-backed forms * Bind forms to workflows, publish them, and test submissions * Configure dynamic option sources and collection tables #### Apps and dashboards * Build apps, dashboards, portals, and pages * Wire up data sources, selectors, tables, and interactive controls * Publish and verify that bindings and interactions work #### Integrations and credentials * Build integrations for any app or tool from scratch: The Rewst Agent can use API docs you submit, or perform web lookups for you if the documentation is public * Check which integrations you have installed and configured * Help set up authentication methods: OAuth, API keys, etc.
#### Microsoft CSP / GDAP * Work with customer-scoped Microsoft Graph operations across tenants * Check connection status, permissions, and GDAP scope * Run delegated operations for your CSP customers #### Data and execution - [Fabric](/rewst-documentation/documentation/rewst-agent/fabric-in-rewst.md) * The Rewst Agent can interact with Rewst's persistent, key-value data store * Key-value data storage lets workflows save or read named values that persist between runs and across workflows * Beyond holding configuration and per-organization settings, it lets a slow or expensive workflow store its result once, so that other workflows, forms, or apps can read it instantly, instead of waiting on that workflow to execute every time * Query live data from your connected tools - tickets, companies, users, devices, etc. - without the need to create persistent workflows * Fetch and combine paginated results to answer questions about your environment #### Marketplace * Browse the Marketplace, view installed Crates, and help with publishing and installing #### Navigation and guidance * Jump you to platform sections as needed * Explain Rewst concepts and MSP terminology * Answer conceptual "how does this work?" questions ## Troubleshooting Ask the Rewst Agent questions about the platform and get instant guidance. The Rewst Agent also understands your Rewst environment— your workflows, variables, and executions— so you can ask things like ‘Why did this workflow fail yesterday?’ Paste an error into the chat or ask why a run failed, and the Rewst Agent will break it down, point to the issue, and suggest what to do next. If something isn't working in Rewst, your first step should be to ask the Agent why. ## Mock mode When you run a workflow, you have the option to use *mock mode*. Rather than reading from or writing to your live Rewst environment, the Rewst Agent will run the workflow using sample inputs and outputs instead. This lets you confirm that your workflow behaves correctly before it ever touches real data. ## What can't the Rewst Agent do or help with? Most of the things the Rewst Agent can't do come down to secrets, consent, external systems, and judgment calls. It's blocked in places where it either can't hold the credential, can't click through a browser, or shouldn't be the one deciding. #### Authentication and secrets * **The Rewst Agent can't input** API keys, client secrets, passwords, tokens. It can create an authentication method and set up the step structure, but you'll need to type the actual secret into the Credentials screen in Rewst. * It's blocked from completing OAuth browser flows: the interactive consent or login screens, MFA prompts, or "Accept permissions" dialogs. I can build the flow, but you'll need to click through it. * Microsoft admin consent and CSP reconnection must be done manually. This includes granting delegated permissions, accepting GDAP role requests, and reconnecting a disconnected CSP link in Partner Center. #### Connect and configure external systems * When setting up the vendor side of a webhook — e.g., pasting a Rewst webhook URL into your PSA/RMM/third-party console — the Rewst Agent can build the trigger only. The external registration is your responsibility. * The Rewst Agent can't configure anything outside Rewst. This includes DNS records, firewall rules, mailbox and transport settings, permission scopes in your PSA or RMM, and licensing. * It also can't grant the underlying API permissions. If a Microsoft Graph call needs a scope that isn't consented yet, only an admin can approve it. #### Purchases and agreements * The Rewst Agent won't be able to accept terms or make purchases. This is relevant when installing Crates that require an agreement, anything with a "I agree" or billing step. #### Decisions and data The Rewst Agent can't: * Make business judgment calls — which board or queue or company or priority to use when more than one plausibly fits, or how to interpret an ambiguous requirement. It will ask rather than guess. * Complete real-world verification — confirming a change actually landed correctly in the target system from an end-user's perspective, or validating business correctness of results. * Provide data that isn't discoverable — sometimes it needs you to provide a specific record ID or name that isn't safely queryable. #### Approvals and outward-facing actions The Rewst Agent can't authorize anything that writes to or notifies the outside world. It will always pause for your explicit go-ahead before creating, sending, or mutating external records. That approval doesn't carry over to the next approval gate. --- # 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.rewst.help/rewst-documentation/documentation/rewst-agent/rewst-agent-capabilities.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.