Glossary

Your personal user profile, identified by your email address. It travels with you across workspaces, while your workspace role controls what actions you can perform.

A Step that performs an external or built-in operation. Examples include sending an email, updating a CRM record, or running code.

The right-hand configuration panel for a selected Step. It provides Setup, Executions, and Test & Debug tabs, where tests can perform real actions in connected services.

A set of connected Steps built on the canvas. It combines triggers, actions, data transformations, and flow controls in sequence.

The workspace billing page at /app/subscription. It shows usage meters, published unit prices, invoices, payment methods, and billing safeguards based on your billing permissions.

The multiplayer visual workspace for building and operating automations. It renders triggers, action Steps, routing branches, sticky notes, and live collaborator cursors.

A client organization’s workspace managed under a delegation grant. The grant controls operational access without creating a billing agreement.

A flow control Step that evaluates structured rules. Every matching branch runs, while an optional Else branch runs when no rules match.

A connected app account authenticated via OAuth or API credentials. Steps use the selected connection within that account’s permissions.

A data Step that formats, compares, and shifts timestamps. It can also extract calendar parts such as month or weekday.

One run of an automation started by a trigger or test. An execution ID links its Step attempts, inputs, and outputs.

The dock group of built-in logic Steps. It includes Conditions, Switch, Filter, Repeater, Wait, Human Review, Stop and Error, and Do Nothing.

The consumption unit for hosted AI features in Glow. Billable usage equals input, output, and reasoning tokens, resets monthly, and never converts into Step credits.

A delegation agreement from a client Admin to a partner. Grants specify the access tier (Read-only or Full operational), covered automations, expiration, and audit logging.

Manual field configuration for an eligible app action in the App drawer. Select it from the HTTP | MCP toggle in the Step’s ⋮ menu; it is distinct from the HTTP Request Step.

A built-in Step under Tools → Data → Dev tools for custom HTTP calls. It supports GET, POST, PUT, DELETE, and PATCH within authentication, timeout, and payload limits.

The canvas drawer that turns an automation into a standalone form. Users submit inputs without opening or modifying the canvas.

The directional wire connecting two Steps on the canvas. Step B runs after Step A finishes and can read Step A’s outputs.

Repeated execution over a list. Run for each item repeats a single action Step over a list, while Repeater repeats a multi-Step loop body.

Natural-language configuration for an eligible app action in the App drawer. Select it with the HTTP | MCP toggle in the Step’s ⋮ menu, or switch to HTTP for manual fields.

An open standard connecting AI clients to external tools. Glow provides an MCP server for AI editors and an MCP client for AI Agents.

A billing model using purchased Step credits, Glow AI tokens, and retained storage. Exhausting a balance pauses new work requiring that resource without reversing completed external actions.

A structured key-value data object such as a contact or invoice. Steps pass, map, and transform collections of records across an automation.

Persistent workspace cloud storage (in GB) for files and documents. Retained storage is standing capacity and never resets monthly.

A workspace user’s permission tier: Admin, Manager, Member, or Viewer. Admins, Managers, and Members build and run accessible automations, while Viewers see permitted diagrams and run summaries, not configuration or execution payloads.

A built-in trigger that starts runs on a recurring schedule. Configure it using plain-language intervals or cron expressions.

The trigger or Step selected in the dock when starting a manual test run.

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

A unit used to meter automation actions. Consumption depends on the action’s published rate and work performed, and some actions cost no Step credits.

A canvas Step that runs another automation as a child routine. It waits for the child run’s result before continuing.

A routing Step that checks ordered cases against an input value. It runs only the first matching branch or the fallback.

The shared organizational unit for automations, connections, variables, files, and billing. Member roles and visibility settings govern access inside a workspace.

A reusable automation blueprint from the Marketplace or your team library. Fork it into a workspace canvas to customize and run it.

The entry Step that starts an automation run. Examples include Webhook, Scheduler, Chat Trigger, Form Trigger, and app events.

A flow control Step that pauses execution for up to 13 days. The run resumes automatically when the timer elapses.

A trigger Step that exposes an HTTPS endpoint for incoming requests. It supports optional HMAC signature verification and synchronous responses.

A synonym for an automation built and run on the canvas.

The data picker opened from a field’s data icon. It inserts references using retained outputs, saved test data, or predicted fields. Check the actual output before relying on a suggested field.

The team environment you are currently operating in. Access depends on your role, automation visibility, and any active delegation grant.