Skip to content

Glossary

Every Flero term in one place. Words used in this guide are defined here; this is the canonical reference.

Action node: A node that does something during a run (calls an API, transforms data, sends a message). Contrast with a trigger node, which only starts a workflow.

Active version: The saved version of a workflow that automatic triggers (webhook, schedule, connector events) run. Set it with Make version active. See Versions and activation.

AI budget: A monthly spend limit for AI in a workspace, set separately for AI Agent nodes and the AI builder chat. See AI budgets.

AI builder: The chat assistant in the editor that builds and edits workflows from a description. See AI builder.

API key (Flero): A key that lets your own systems call the Flero API, sent in the x-api-key header. Keys start with dk_ and carry scopes. See Authentication and API keys.

Approval: A workflow step that pauses the run until someone approves or rejects it. The first decision wins. See Approval basics.

Approval link (public): A one-time URL (/approvals/public/:token) that lets someone respond to an approval without logging in. A new link is created each time the run pauses.

Archive: Moving a workflow out of the main list without deleting it. Archived workflows can be restored. See Archive and restore.

Canvas: The drawing area in the workflow editor where you place nodes and draw connections. Supports pan and zoom.

Chat trigger: A trigger that starts a workflow from a chat dialog in the editor. See Chat trigger.

Connection: A line between two nodes; data flows along it from one node's output port to the next node's input port.

Connector: A pre-built integration with an external service (Slack, HubSpot, Granola and others). Each connector exposes a set of operations and uses a credential. See the Connector catalog.

Credential: A stored secret (OAuth token, API key, username and password) used by a connector or HTTP node to authenticate against an external service. Credentials are encrypted at rest. See Managing credentials.

Credential scope: Who can use a credential: Personal (just you), Workspace (everyone in the workspace) or Organization (every workspace in the organization). Scope can't change after creation.

Edge: Synonym for connection.

Execution: A single run of a workflow. Has a unique ID, a status (pending, running, paused, waiting_for_input, waiting_for_human, success, failed, timeout, stopped), input data, output data and per-node timings. See Execution lifecycle.

Execution detail: The view of a single execution (/logs/:id). Shows metrics, a timeline, the workflow structure and the final output.

Execution ID: The unique ID of one run. Copy it from the Logs table or the execution detail page.

Expression: A path inside {{ … }} that looks up data at run time. Example: {{ $node["Get user"].output.response.body.name }}. Expressions look values up; they don't calculate. See Expressions.

Flero: The platform you're using: visual workflow automation for the enterprise.

Flow control node: A node that changes the path of a run rather than transforming data: If, Switch, Loop, While, Merge, Delay, Approval.

Folder: A way to group workflows in the Workflows list. See Folders.

Form trigger: A trigger that starts a workflow when someone submits a form. Generates a public form URL.

Logs: The screen (/logs) that lists every execution in your workspace, with search, filters, saved views and export. See Logs.

Loop: A flow-control node that runs the downstream nodes once for each item in a list.

Manual run: Starting a workflow by clicking Run Workflow or Test Run in the editor, or through the API.

MFA (multi-factor authentication): A code from an authenticator app, required at sign-in in addition to your password. Turn it on in Settings → Account. See Security & MFA.

Mock data: Stand-in responses used during sandbox runs. See Mock data.

Node: The building block of a workflow. Each node performs one action. Nodes have input and output ports, configuration fields and runtime state.

Node panel: The panel that opens on the left of the editor when you select a node. It has Settings, Schema and JSON tabs. Several can be docked at once.

Node palette: The list of available nodes in the editor, grouped by category. Click or drag to add a node to the canvas.

Operation: One specific thing a connector can do (for example Slack's Send). A connector node runs one operation.

Organization: The top-level container above workspaces, with shared members, settings and credentials. See Organization settings.

Output port: A connection point on a node where data exits. Most nodes have one (output). Some have several, for example If has true and false, and many nodes have an error port.

Pin Data: Saving a node's output so later runs reuse it instead of running the node. Pinned nodes are skipped in every run, Production included.

Port: A connection point on a node. Input ports receive data, output ports emit it.

RAG (retrieval-augmented generation): A pattern that grounds an AI answer in your own documents by retrieving relevant chunks first. Flero has nodes for chunking, embedding, vector search and reranking. See RAG nodes.

Recipe: An end-to-end tutorial in Recipes that builds a complete workflow for a real scenario.

Rerun: Starting a finished run again with its original trigger data. Creates a new execution. See Rerun, stop & pause.

Run: Synonym for execution.

Sandbox mode: A run mode that answers outside calls with mock data, so you can test workflows safely. Switch between Sandbox and Production in the editor header. See Sandbox mode.

Schedule trigger: A trigger that fires on an interval or a cron expression.

Scope (API key): What a Flero API key is allowed to do. New keys are read-only by default.

Sticky note: A text note on the canvas for documenting a workflow. See Sticky notes.

Sub-workflow: A workflow run as a single node inside another workflow. Lets you build larger automations from reusable pieces. See Sub-workflows.

Template: A workflow you copy as a starting point, from the Templates card in the editor's node panel. See Templates.

Test Run: Running a workflow from the editor in Sandbox mode.

Trigger: A node that starts a workflow. See Triggers.

Version (workflow): A saved snapshot of a workflow, shown as a chip such as V12. One version can be active.

Webhook: A URL Flero generates for the Webhook trigger. A request to it starts a run.

Workflow: A graph of nodes and connections that defines an automation. Has a name, a status, versions and an owner.

Workflow editor: The visual canvas screen (/workflow/:id) where you build workflows.

Workflow ID: The unique ID of a workflow, used in API calls and shown on the execution detail page.

Workspace: Your team's container for workflows, credentials and executions. Members share it; permissions are role-based.

Workspace variable: A named value set in Settings → Workspace, read in expressions with $env. Variables can be marked secret.

$env.NAME: Expression reference to a workspace variable. An unset variable fails the node.

$input: Expression reference to the data entering the node.

$node["Name"]: Expression reference to another node's data, by its display name. Read its result under .output.

$trigger: Expression reference to the data that started the run. A webhook or form body is under $trigger.payload.

$workflow: Expression reference to the workflow's id, name and variables.

Found something out of date? This page lives in the Flero docs content set.