Core concepts: workflows, runs and nodes

Workspace

A workspace is your team's account. It has its own members and roles, its own plan, its own credential vault and AI provider keys, and its own workflows. Data from one workspace is never visible in another; this is enforced in the database with row-level security.

Workflow

A workflow is a graph of nodes connected by edges. Every workflow has exactly one trigger node (where a run starts). Saving a workflow is enough for it to be used — there is no separate publish step; schedules and webhooks always use the saved workflow.

Run

A run is one execution of a workflow. Each run has a status (running, success, error, paused, cancelled or timed out), a duration, a mode (dry or live), what triggered it, and a step-by-step trace. Dry runs happen in your browser; live runs happen on the server.

Node types

Node	Purpose
Trigger	Where a run starts: Manual (Run button), Scheduled, Webhook, or App event (a new row, contact or message in a connected app).
Action	Does something: AI Generate, HTTP Request, Webhook Call, Send Email or Slack Post.
Agent	An AI step that can reason over several steps and call the HTTP request tool.
Observer	An AI step that reviews the run so far and reports insights on errors, performance and cost.
Router	Sends the run down the first route whose conditions match, with a default fallback.
Transformer	Reshapes data (field mapping, templates, normalising contacts, building API payloads).
Validator	Checks data against rules or a schema and routes it to pass or fail.
Guardrail	Blocks or warns on banned terms or fields.
Human Review	Pauses the run until someone approves or rejects it in the Review Queue.
App action	Does something in a connected app (post to Slack, add a sheet row, create a HubSpot contact…), or sends a custom request to any API.
Memory	Stores and reads values, optionally persisted across runs.
Retriever	Looks up relevant entries from workflow memory or static data.
Loop	Runs the following steps once per item in an array.
Error Handler	Catches failures from earlier steps so you can recover or report them.
Sub-workflow	Calls another workflow as a step.
Output	Delivers the result: Publish Output (webhook, HTTP, email, Slack), Send Email or Generate File.

See the Node reference for what each node configures and when to use it.

Agent

Agents come in two forms. The Agent node is an AI step you configure yourself on the canvas (prompt, model, tools). The agent marketplace offers 219 pre-built agents in 30 categories that your workspace can unlock; Pro, Business, Elite and Enterprise plans include some for free. Each marketplace agent has its own setup guide under /docs/agents.

Credential

A credential is a secret (API key, bearer token, basic auth, custom header) stored encrypted in your workspace's credential vault. Steps that call external services and webhook triggers can reference a credential instead of holding the secret in the workflow itself.

Integration

An integration is a connection to a third-party app. Airtable, Asana, beehiiv, BigCommerce, Bluesky, Bullhorn, ClickUp, Close, DAT, Discord, Discord (channel webhook), eBay, Gmail, Google Ads, Google Calendar, Google Contacts, Google Docs, Google Drive, Google Forms, Google Sheets, Greenhouse, Gumroad, Housecall Pro, HTTP / Custom API, HubSpot, Kit, Klaviyo, Lemon Squeezy, LinkedIn, LinkedIn Ads, LinkedIn Conversions, Mailchimp, Mastodon, McLeod (LoadMaster / PowerBroker), Microsoft Excel, Microsoft Teams, monday.com, Notion, OneDrive & SharePoint, Outlook Calendar, Outlook Mail, Patreon, Pipedrive, Printful, Printify, QuickBooks Online, Salesforce, ServiceTitan, Shippo, Shopify, Slack, Square, Stripe, Tai TMS, Teachable, Telegram, Trello, Truckstop, Twilio, Twitch, Typeform, WooCommerce, Xero, YouTube and Zoho CRM are available; 11 more apps are in beta (connectable, still being tested against real accounts) and Gmail inbox and Google Business Profile are coming soon. Each app brings actions (used in App action steps) and, for many, events that start workflows (App event triggers). The full list is under Integrations & credentials.

Trace

A trace is the step-by-step record of a run: which nodes ran, in what order, what they received and returned, how long they took and any errors. Open it in the workflow panel's Trace tab.

Workflow version

A version is a saved snapshot of a workflow's graph. Pressing Save creates a version; autosave also records one at most every few minutes when something changed, and you can save a labelled version from the Versions tab. You can restore any version (restoring creates a new version, so it can be undone) or export it as a .fluxo.json file (secrets removed; see Import & export).