Patterns

Agent-ready Business Action v2

Expose an existing domain capability to agents through a narrow MCP Workflow rather than giving the agent direct provider credentials or a generic integration surface.

Avoiding SQL Injection Attacks

SQL Injection is a technique that an attacker can use to cause malicious SQL statements to execute, using a legitimate SQL query as a channel.

Cached Result Pattern v1

The Cached Result pattern enables you to improve performance of frequently running Workflows and reduce overhead on internal apps and services by caching data within the platform for a defined period of time.

Collector/Processor Pattern v1

The Collector/Processor pattern allows you to acquire data in one Workflow and process it asynchronously in another Workflow.

Correlate Records Across Systems v2

Correlating records means identifying which records in different systems represent the same business object.

Environment-aware Delivery v2

Deliver the same Workflow contract through Test and later Environments while keeping endpoints, credentials, releases, status, hostnames, and test data isolated.

Eventual Consistency v2

When integrating across multiple services, it is usually not possible to synchronize one transaction across all of them.

Exception Remediation App v2

Use a focused Flowgear App to let authorized operators inspect an integration exception, submit a bounded correction, and invoke an audited remediation Workflow.

Exploratory MCP Tools v2

Exploratory MCP tools are a set of three Workflows that help an agent when it needs to discover an unfamiliar data model in order to select records.

Extract Transform Load ETL Pattern v1

The Extract Transform Load pattern is the most common type of Production ready Workflow.

Factor a Large Workflow v2

Extract a Sub-Workflow when part of a design has a clear contract and a reason to change, test, reuse, or operate independently.

HTTP API Facade v2

Expose a stable HTTP contract in front of provider-specific Workflows so callers do not depend on Connection details, provider schemas, or internal orchestration.

Idempotent Upsert v2

Use a stable business key and deterministic create-or-update rules so retrying the same input does not create a duplicate or apply an unsafe transition twice.

Integrating with SQL databases v1

Flowgear includes the following Connectors for SQL.

Key/Value Tracking Pattern v1

The Key/Value Tracking pattern uses Key/Value Nodes to track data as it moves through an integration.

Local System Integration v2

Use a local Cluster when a Workflow must reach systems or resources that are not available from Flowgear's cloud runtime.

One-To-Many Pattern v1

The One-to-Many pattern enables you to retrieve data from one source and send it to many targets, or retrieve data from many sources and send it to one target.

Repeating an integration with Dynamic Connections v1

Flowgear allows you to inject a Connection ID directly into the Connection Property of a Connector Node.

Utility MCP Tools v2

A utility MCP tool is a Workflow that performs one clear business action.