# More than tests: business logic on your site. > A Bixlow workflow is a declarative, node-based model that combines variables (state), actions (custom JavaScript), bindings (how state shows on the page) and triggers (the events that run actions), injected into the site at runtime. - Source: https://bixlow.com/en/platform/workflows - Language: en - Publisher: Bixlow A workflow describes what state matters, what runs, when, and how it shows on the page. The agent builds it, you read it on a node canvas, and it all works without touching the theme. - **Model:** Declarative, node-based - **Building blocks:** Variables, actions, bindings, triggers - **Reuse:** Snippets with history - **Safety:** Versions and loop protection ## When a change stops being "edit some copy" A free shipping threshold that updates with the cart, or a multi-step form, doesn't fit in a copy editor. It shouldn't end up in the theme either. ### Loose scripts pile up Every campaign leaves a JavaScript snippet in the tag manager. Nobody knows what each one does or whether it is safe to remove. ### Logic ends up in the theme What started as a test stays inside the site's code, and undoing it needs a developer again. ### Visual editors fall short They can change a color or a headline, but not make something react to session state, the URL or what the visitor does. ### Every agency rebuilds the same thing The same counter or bar gets coded from scratch for each client, with no reusable piece to maintain. ## How a workflow is built Four building blocks, connected on a canvas. The agent assembles them from what you ask for, and you can open and edit any of them. 1. **Define the state.** Variables hold what matters: a value from the session, from browser storage, from the URL, or derived from other variables. 2. **Write the logic.** Actions are custom JavaScript: what happens when something occurs. The agent writes them and you can read and edit them. 3. **Show it on the page.** Bindings connect state to an element's content, attributes, classes, styles, src, href, visibility or repetition. 4. **Decide when it runs.** Triggers fire actions: on page load, on a DOM event, when a variable changes or when another action finishes. ## A model built to be maintained The hard part is not getting something to work on day one. It is being able to read it, reuse it and remove it months later. ### Declarative model: State, logic and presentation kept apart Every building block has a clear role, so you can tell what a workflow does without reading all of its code. - Session, storage, URL and derived variables. - Content, attribute, class, style, src, href, visibility and repeat bindings. - Triggers on page load, DOM events, variable changes or finished actions. ### Snippets: Reusable pieces with history What you build once is saved as a snippet and reused in other workflows, with its own change history. - One component for several pages or campaigns. - History per snippet. - Available on paid plans. ### Versions: Every change, reversible The workflow saves on its own, keeps a version history and locks the draft while someone is editing it. - Version history with restore. - Autosave and edit lock. - Stopping a workflow removes the change on the next page load. ### Protection: No loops that freeze the site Action chains are protected against cycles, so an action that calls itself can't lock up your visitors' page. - An action chain can't loop back on itself. - The script fails silently if something goes wrong. - To call a server, connect it to Bixlow Functions. ## The agent assembles the workflow; you can read all of it You don't need to draw nodes by hand. Describe what you want and the agent creates the variables, actions, bindings and triggers, and wires them together. ### You decide - What should happen, and on which pages. - Which parts you want to review or edit by hand. - Which pieces become snippets for reuse. - Publishing: nothing reaches your site without your approval. ### The agent does - Creates the variables, actions, bindings and triggers. - Wires a new action to the existing trigger instead of duplicating it. - Writes the JavaScript for each action. - Builds HTML components in your brand's look. ### A workflow in Bixlow - **Goal:** Free shipping bar that updates with the cart - **Variable:** cart_total (derived) - **Action:** updateShippingBar - **Binding:** The bar's text and visibility - **Trigger:** Click on "Add to cart" ## Bixlow Studio: Need something bigger than a change? Bixlow Studio uses the same workflows to build custom features on your site without touching your theme: engineers build them and a strategist reviews them. - Custom components and logic on your site. - Integrations with your CRM, payments or email through Functions. - Reusable snippets for your recurring campaigns. ## FAQ ### Do I need to code to use workflows? No. The agent builds the workflow from what you ask for. If you do code, you can open any node, read its code and edit it. ### How is this different from pasting a script into Google Tag Manager? A workflow separates state, logic and presentation, has a version history and can be stopped: the change disappears on the next page load. A loose script has none of that. ### Do workflows change my theme? No. They are injected into the page at runtime. Your theme is untouched, and undoing a change means stopping the workflow. ### What if an action calls itself? Action chains are protected against cycles, so a loop never gets to freeze your visitors' page. ### Can a workflow call my server or an API? Yes, with Bixlow Functions: server-side code with encrypted secrets that workflows can call. They are on the Premium plan. ## Your first workflow, today Install the script, tell the agent what should happen on your site and review the nodes before publishing.