--- title: "Workflow automation with AI steps and approvals | SalexHub" description: "A trigger on any record, conditions from your views, then steps that update, create, notify, wait or ask an AI step. Every run has a budget and a history." url: "https://salexhub.com/product/workflows" --- # Workflows: When something happens, the next step follows. A trigger on any record, conditions in the same filters as your views, then steps: update a property, create a record, notify a person, wait, or let an AI step judge. Every run has a budget and a history. When a deal is won above AED 50,000, a workflow summarizes it for delivery and creates the invoice from the deal. Issuing the invoice is held by an approval rule until someone approves it. [Start free](https://app.salexhub.com/register) ยท [See pricing](https://salexhub.com/pricing) ## What you do with it **Triggers, steps and waits, on any object.** - **Triggers**: A record is created, changed, deleted, or enters or leaves a list; a property changes to a value; a quote is accepted or an invoice issued. On a website you track, a visit or a form submission. - **Steps**: Conditions with a yes and a no branch, update a property, create a record, add it to a list, notify a person, run another workflow, or use one of the product's tools. - **Waits**: Pause for a set time, or until a date on the record, such as two days before a renewal. The record is read again when the wait ends. - **AI steps**: Ask a model about the record and write the answer to a property, so the next condition can branch on it. It runs on your own key and spends AI credits from the run's budget. - **Drafts, versions, test runs**: Changes to a live workflow stay a draft until you publish. Each time you publish, you get a version you can restore, and a test run on one record writes nothing. - **Run history**: Each run with its status, its record, its steps and the AI credits it spent, and a trace you can replay on the canvas. ## The Agent here **Ask for a workflow in plain words.** The Agent reads workflows and their runs, and drafts a workflow from a conversation. Saving or publishing waits for your approval as a card in every mode, Full autonomy included. Tools from the product's registry that the Agent uses here: - `workflow.list`: Lists the workflows and what each one reacts to. Runs in every autonomy mode. - `workflow.runs`: Reads a workflow's runs and what happened in each. Runs in every autonomy mode. - `workflow.create`: Creates a simple workflow from a trigger and its actions. Asks unless the mode is Full autonomy. - `workflow.save`: Saves a workflow's full graph as a draft. Asks unless the mode is Full autonomy. - `workflow.publish`: Publishes the draft, which makes it live. Asks unless the mode is Full autonomy. ## Connected **A workflow works with the whole product.** - [The Agent](https://salexhub.com/product/agent): An AI step is the Agent inside a run, and each one is listed in Agent > Tasks. - [Control & audit](https://salexhub.com/product/control): An approval rule holds a workflow's act the same way it holds anyone's, and the run stops there. - [Objects & data](https://salexhub.com/product/objects): Workflows run on any object, your own included, and on the steps of quotes, invoices, orders and leave. - [Reports & dashboards](https://salexhub.com/product/reports): A goal falling off pace, or a decision due for review, can start a workflow. ## Control **Guardrails on every run.** - Each run has a budget: 100 steps and 50 AI credits by default, which a workflow can raise. - A record change made by a workflow never triggers another workflow. Only a Run workflow step starts one, and loops are refused when you save. - A failing workflow never undoes the change that started it. - A workflow runs as itself, not as a person: its steps still meet your approval rules, and it never touches a record marked Do not automate. - Only Owners and Admins build and publish workflows. ## Recent changes - 2026-09-21 (Workflows): **Workflows run on their own, with approval rules on single steps.** A published workflow runs its steps without an admin on every run, and a step that needs a yes is held by an approval rule like anyone else's action. - 2026-08-23 (Workflows): **Workflow drafts, versions, test runs and waits.** Editing a live workflow saves a draft you publish when ready, each publish is a numbered version, a test run shows what would happen, and a Wait step pauses a run until a time or a date on the record. - 2026-08-14 (Workflows): **Any action as a workflow step.** A step can run any action the platform offers rather than a short fixed list, and an AI step calls the tools you allow it. All changes: [Changelog](https://salexhub.com/changelog) ## Read more - [Approval rules](https://salexhub.com/docs/control/approval-rules): Hold a single step until someone approves it. - [Webhooks](https://salexhub.com/docs/developers/webhooks): A signed delivery to your endpoint when a record changes. - [One registry for the Agent, workflows and the API](https://salexhub.com/blog/one-registry): Why a workflow step meets the same approval rules as the Agent. --- The same page for people: https://salexhub.com/product/workflows. Index of this site for agents: https://salexhub.com/llms.txt