Describe the job.
Write what you want done in plain words. The advisor reads all 23 capabilities, proposes steps built only from ones that exist, and names anything it cannot do rather than inventing a step for it.
Workflows live in your account.
The advisor writes a workflow for you and charges credits for it, so it needs an account to charge and somewhere to save the result.
A workflow is a saved chain of ToolForte capabilities that runs in one call. You build it once, test it against real input before you save it, and then run it from the browser, over the REST API, or from an MCP client. Every run draws on the same credit balance as everything else, so there is nothing extra to buy.
They are tied to an account because they are stored per person, and because a run spends credits. A free account is enough to build one and run it.
Nothing here needs an account to read: the tools run in your browser, the API docs list every capability a workflow can call, and the MCP page explains how an agent reaches them.