Glossary

Your personal user profile identified by your email address. Your account travels with you across every workspace you belong to. What actions you can perform inside a given workspace is determined by your role in that workspace, not your account.

A type of step that executes an active task: dispatching an email, creating or updating records in a CRM, querying a database, or evaluating custom code. Actions are the executable operations of a workflow, distinct from triggers and flow controls.

The right-hand configuration panel that opens when you select any step on the canvas. The App drawer provides tabs for Setup (input fields and data mappings), Executions (step output history), and Test & Debug (isolated test runners).

The administration hub located at /app/subscription where teams monitor live meters (Step credits, Glow AI tokens, Retained storage), review published pricing calculators, configure budget safeguards, manage payment methods, and download PDF invoices.

The real-time multiplayer visual workspace where workflows are designed, wired, tested, and operated. The canvas renders triggers, action steps, routing branches, sticky notes, and live collaborator cursors.

An isolated tenant workspace belonging to a client organization, managed by a consultancy or MSP through an authenticated delegation grant. Workflows, credentials, logs, and billing remain strictly segregated from all other tenants.

A flow control step that evaluates structured rules and routes workflow execution down matching branches. Each matching rule triggers its own path, while an optional ELSE branch executes when no rules match.

An authenticated third-party OAuth token or API credential securely stored in the workspace. Workflows bind to connections to interact with external services on behalf of your team.

A data transformation step that formats timestamps for human readability, computes intervals between dates, adds or subtracts time offsets, or extracts components (e.g. month, weekday).

A discrete run of a workflow initiated by a trigger or manual run point. Each execution maintains its own isolated context, step logs, input payloads, and output states.

The dock group of built-in logic steps that control execution flow: Conditions, Switch, Filter, Repeater, Wait, Human Review, Stop and Error, and Do Nothing.

The consumption unit for hosted AI features in Glow (AI Prompt, AI Agent, AI Data Transform, Workflow Assistant). Total billable tokens equal input tokens + output tokens + reasoning tokens. AI tokens never convert into Step credits and reset monthly.

The formal delegation agreement granted by a client Admin to an external MSP or consultancy. Grants specify access tiers (Audit, Standard, Full Operational), covered workflows, expiration dates, and audit logging.

The deterministic configuration mode on a step where you explicitly specify input fields, values, and variable mappings, ensuring identical execution on every run.

A built-in action step located under Tools → Data → Dev tools that makes custom REST API calls (GET, POST, PUT, DELETE, PATCH) to any publicly accessible web service.

The canvas drawer that transforms a backend workflow into an interactive standalone form. End-users fill in input fields and submit requests without opening or modifying the workflow canvas.

The directional wire connecting two steps on the canvas. An edge defines data dependency and execution order: Step B executes after Step A completes, with Step A’s outputs available to Step B.

Glow provides two looping mechanisms: Run for each item (a setting on a single action step to iterate over a list) and Repeater (a canvas step that repeats a multi-step workflow body).

An authoring toggle on steps that lets you describe intended behavior in natural language, which an AI model interprets to populate fields. For deterministic production runs, use HTTP Mode.

An open standard connecting AI coding assistants (Cursor, Claude Desktop, Zed) to Glow as an MCP Server for workflow discovery and step sandboxing. Glow also acts as an MCP Client allowing canvas AI Agents to call external tool servers.

Glow’s resource-based billing model where workspaces configure independent monthly allowances for Step credits, Glow AI tokens, and Retained storage in advance. When an allowance depletes, operations pause safely without surprise fees.

A structured key-value data object (such as a customer contact, CRM lead, or invoice). Collections of records are passed between steps, mapped into fields, or transformed using data helpers.

The root property key under which connected App action steps and HTTP Request steps store their returned response payload (e.g. {{ 3.ret.id }}). Triggers store output at the root without ret (e.g. {{ 1.id }}).

The persistent cloud storage capacity (measured in Gigabytes) allocated to a workspace for stored files, attachments, and generated documents. Storage represents continuous standing capacity and never resets monthly.

The permission tier assigned to a workspace user: Admin, Manager, or Member. All three roles can build, edit, and run workflows. Financial management and team settings are restricted to Admins.

A built-in trigger step that automatically initiates workflow runs on a recurring schedule (e.g. every weekday at 9:00 AM) using plain-language schedules or manual cron expressions.

An encrypted workspace credential (such as an API key, signing secret, or password). When referenced in workflows, secret values are automatically masked with [REDACTED] in execution logs.

The specific trigger or step selected in the canvas dock when performing manual test runs on multi-trigger workflows.

The fundamental building block on the Glow canvas. Every trigger, action, AI model, and flow control element is a Step identified by a permanent step number.

The execution unit in Glow. Each executed non-AI step consumes 1 Step credit. Control steps (Wait, Human Review, Do Nothing) consume 0 credits. If a step fails prior to external work, the reservation is released.

A canvas step that executes another workflow as a modular child routine and waits for its return payload before continuing.

A data step that aggregates arrays into grouped statistical summaries (count, sum, average, min, max) under {{ N.groups }}.

A routing step that evaluates ordered cases against an input value and executes the first matching route (or a fallback branch).

The shared organizational unit in Glow. Workflows, connections, secrets, files, and execution logs belong to the workspace rather than individual user accounts.

A pre-built workflow blueprint from the public Marketplace or your team library that can be forked into a canvas to accelerate development.

The initial step that starts a workflow run (e.g. inbound Webhook, Scheduler timetable, App event, or Chat trigger). Workflows can feature multiple triggers.

A named data value referenced across workflow steps using {{ N.field }} placeholders. Ephemeral variables exist within a single run, while persistent variables live in workspace settings.

A flow control step that suspends workflow execution for a defined duration (up to 13 days), resuming automatically when the timer elapses.

A trigger step that exposes an unguessable HTTPS endpoint to ingest real-time JSON payloads from external applications, with optional cryptographic HMAC signature verification.

An end-to-end automation graph created on the canvas, composed of one or more triggers, action steps, data transformations, and flow controls connected in sequence.

The interactive data picker opened from the icon beside any step field, listing exact outputs produced by earlier steps to insert verified variable tags into your configuration.

The active organizational tenant context you are currently operating in, isolating workflows, connections, variables, files, and billing.