Concepts

Account and Subscription

An Account is the ownership and commercial boundary for Flowgear subscriptions and published Apps.

Activation Modes and Timeouts v2

The Runtime changes how a Workflow behaves according to why it was started and whether it is using the current design or a published revision.

Always On v1

Always On is the term used to describe a Workflow that executes continuously until explicitly stopped.

API Key

An API Key defines who or what may invoke a selected set of Workflows in one Site Environment.

App security model v2

Flowgear separates an App's user interface from the authority to run its backend workflows.

Apps v2

Flowgear Apps are lightweight interfaces over Workflow-backed business logic.

Audit Trail

The audit trail records supported platform changes and security-relevant operations for an object or scope.

Compiled execution v2

The Runtime converts a Workflow definition into an executable artifact as part of publishing it.

Configure Variable Bar v1

Properties can be added to the Variable Bar by clicking the + icon, existing Properties can be edited or removed by clicking on the Name of an existing Property.

Configure Workflow Screen v1

The Configuration variables screen manages values for Configuration Variable Properties used by a v1 Runtime Workflow.

Connection

Connection identity and Environment values are shared platform concepts, but creation, assignment, and execution placement differ by runtime.

Connection v1

A Connection is a reusable configuration for accessing a service or data source.

Connection v2

A Connection is a reusable configuration for accessing a service or data source.

Connector Node Type v1

A Connector is a wrapper around a third party app or service and typically interfaces with it via its API.

Data mapping v2

Data mapping assigns values to the Properties that consume or expose data in a Workflow.

Dropdown

Holds predefined values in a dropdown menu.

DropPoint v1

A DropPoint is a Windows Service that is installed on to a Windows server or workstation in order to enable Flowgear to access data sources that are not exposed to the Internet.

Embedded CSharp Scripts v2

Workflows can include custom C# Scripts that can optionally reference Nuget packages.

Error Handling v2

The Runtime records a failing Step in Workflow Logs and stops normal execution unless an enclosing Try/Catch handles the exception.

Evaluator Node Type v1

Evaluators assess a condition and typically run In Cloud.

Execution order v2

The Runtime executes a Workflow as an ordered tree of Steps.

Flow Connector

Canvas connections have different meanings in each Workflow designer.

Flow Connector v1

A Flow Connector is a visual connection between Nodes or Node Properties in a Workflow.

Flow Connector v2

Canvas connections visualize data dependencies between Properties.

Flow Socket v1

A Flow Socket is a target for a Flow Connector that may appear to the left (input) or right (output) of a Node Property.

Folders

Folders organize objects within a Site.

How Concurrent Workflows Are Measured

Each Flowgear subscription provides a Concurrent Workflow capacity that can be allocated to Sites.

Keys and Identifiers

Flowgear objects have stable keys that are separate from editable display names.

Lazy Evaluation and Streaming v2

The Runtime defers consumption of Streams and Arrays until the Step that requires the data executes.

Microsoft Entra Registered Application

Several Flowgear nodes use Microsoft OAuth authentication to connect to Microsoft cloud services on behalf of a user.

Node

A Node provides an operation that a Workflow can use, such as calling an external service, transforming data, or controlling execution.

Node v1

Nodes (sometimes referred to as Connectors or Adapters) are the elements that are dropped on to the Workflow Canvas in order to describe an integration process.

Node Header v1

The Node Header displays the Icon and name for the Node.

Node Property v1

Node Properties enable interaction with the Node by providing a set of inputs and outputs and are composed of four visual areas.

Node Sample

Node Samples provide sample values for Properties on a Node.

OAuth

OAuth (short for Open Authorization) is a secure way for apps like Flowgear to access your data in another service - without needing your username or password.

Platform Object Model

This article discusses the types of objects that exist within a Flowgear Tenant and their relationnships with each other.

Processor Node Type v1

Processors deal with processing data internally.

Relationships and Last Used

Relationships show how platform objects depend on one another in a selected Environment.

Revisions and releases v2

Flowgear separates a Workflow's editable source history from the revision that each Environment runs.

Run From v1

By default, Nodes execute from within the Cloud runtime.

Run Now

On-demand execution differs by runtime.

Run Now v1

Run Now starts a published Workflow on demand from Console or through its configured API interface.

Run Now v2

The Workflow designer's Run action starts a Debug activation of the current design.

Run Now Screen v1

The Run Now screen provides a way to start a Workflow without opening its designer.

Runtime Cluster v2

Workflows execute on a Cluster.

Site

A Site is the main workspace and permission scope for a set of Flowgear solutions.

Site Environment

A Site Environment is an ordered execution and release boundary within a Site.

Site Settings

Use Site settings in the Console to change Site identity, time-zone and security settings, manage Environments, and configure version control and Release Management.

Sub-Workflows v2

A Sub-Workflow is a published Workflow called from another Workflow.

Tenant

Your Tenant is the top-level Flowgear identity and administration boundary.

Trigger Node Type v1

Triggers block until a condition (such as a time interval, change in filesystem or arrival of email in a mailbox) is met.

Triggers v2

A trigger defines how a published Workflow receives a new activation.

Workflow

A Workflow describes a series of steps for an integration or business process.

Workflow v1

A Workflow is a visual representation of an integration or business process.

Workflow v2

A Workflow is a description of an automation or integration.

Workflow Canvas

The Workflow Canvas uses a different authoring model in each runtime.

Workflow Canvas v1

The Workflow Canvas is the visual design area for Nodes and Flow Connectors.

Workflow Design Basics

Workflow authoring differs substantially by runtime.

Workflow Design Basics v1

A v1 Runtime Workflow is a visual graph of Nodes joined by execution and data Flow Connectors.

Workflow Design Screen

The Workflow Design screen belongs to the v1 Runtime.

Workflow Design Screen v1

The Workflow Design screen is the v1 Runtime design surface for composing Workflows on the visual Canvas.

Workflow Design Settings Screen v1

The Workflow settings dialog configures identity, logging, activation, HTTP binding, and supported MCP options for a v1 Runtime Workflow.

Workflow Landing Screen

The Workflow landing screen provides runtime-aware actions for a selected Workflow, including design, logs, active-instance stop, v2 Runtime status, and applicable v1 Runtime actions.

Workflow Logging v2

The Runtime records each Step in a Workflow execution including capturing Parameters, Returns, timing, result, errors, and parent/child context.

Workflow Logs Screen

Workflow log capture and designer integration differ by runtime.

Workflow Logs Screen v1

The Workflow Logs screen lists each executed Node with its timing, description, result, Execution Output, and captured input and output Properties.

Workflow State v2

The Runtime keeps transient state for each Workflow activation.

Workflow Status v2

Workflow status controls whether the runtime may start a Workflow in a specific Site Environment.