TIBCO Flogo® (formerly known as TIBCO Flogo® Enterprise) enables AI orchestration and intelligent automation through a visual flow designer integrated into Visual Studio Code. Built on a high-performance Go (Golang) engine, it delivers superior runtime efficiency, an ultra-light memory footprint, fast startup, and low-latency processing across edge, cloud, serverless, and on-premises environments. With its AI-ready architecture and powerful set of connectors, Flogo® transforms enterprise data into intelligent, event-driven, AI-ready workflows. To understand all the capabilities, see Build Event-driven Apps with an Ultralight Framework.

What's new in version 2.26.6 (July 2026)

• New String Padding Functions: Two new string functions, string.padLeft and string.padRight, are now available to provide enhanced string manipulation capabilities. These functions ensure your strings meet specific length requirements by either padding them or returning them unchanged if they already meet the criteria. For more information, see String Functions.

• Custom Tags for Tracing and Metrics: You can now enhance tracing and metrics with Custom Tags at the trigger and activity levels within your Flogo applications. Use the new environment variables FLOGO_OTEL_TRACE_USE_CUSTOM_TAGS and FLOGO_OTEL_METRICS_USE_CUSTOM_TAGS to control whether these tags are applied to traces and metrics. For more information, see Adding Custom Tags to Traces and Metrics.

• TIBCO Flogo® Design Assistant - Tech Preview:

  • Configure trigger parameters: The Flogo Design Assistant (FDA) now supports configuring all four trigger parameter groups — Output Settings, Map to Flow Inputs, Reply Settings, and Map from Flow Outputs — enabling comprehensive trigger handler setup.

  • Configure flow input and output parameters: The Flogo Design Assistant (FDA) now supports configuring flow input and output parameters using natural language prompts, enabling you to define schemas for a flow's inputs and outputs within your application.

  • Configure activities with user-defined schemas: The Flogo Design Assistant (FDA) can now configure activities, such as Mapper and InvokeRestService, with user-defined schemas. You can create a schema and attach it to an activity's input or output.

  • Configure REST trigger using an OpenAPI specification: When you create a REST trigger using a user-provided OpenAPI specification, the Flogo Design Assistant (FDA) now automatically enables the Configure Using API Specs option in the REST trigger and binds the specification to the trigger.

  • Reference configuration types for set-attribute: The set-attribute (sa) command now supports four reference configuration types — spec, app-property, schema, and connection — in addition to the existing primitive types. Use these types to bind a trigger or activity settings field to a named project artifact. FDA resolves the artifact name to the canonical Flogo reference string: spec://<spec-id>, =$property["<property-name>"], schema://<schema-name>, or conn://<connection-id>.

  • Field mapping, schema, and expression commands: The Flogo Design Assistant (FDA) now includes a new category of commands for managing field mappings, schemas, and expressions: list-functions, describe-mapping-fields, list-mapping-sources, set-mapping-schema, remove-mapping-schema, make-mapping, remove-mapping, wire-trigger-handler, list-mappings, and check-mappings.

  • Generate MCP Server Tools from API Specifications: Flogo Design Assistant (FDA) now includes a new tool that allows you to generate MCP Server tools directly from an API specification. This streamlines the process of creating server implementations based on your defined APIs, accelerating development and ensuring consistency with your API contracts. For more information, see TIBCO Flogo® Design Assistant - Tech Preview.

• Concurrent Execution of Activities in Parallel Transition Branches (Flow Action): When you set the environment variable FLOGO_FLOW_EXECUTE_BRANCHES_CONCURRENTLY to true, the engine can run the parallel transitions or branches concurrently instead of one after another. For more information, see Concurrent Execution of Activities in Parallel Transition Branches.

• TIBCO Flogo® Connector for Model Context Protocol (MCP):

  • OAuth 2.0 authentication support for MCP Server trigger: A new OAuth 2.0 authentication mode enables the MCP Server trigger to validate incoming bearer tokens against a configured JWKS endpoint. Per-handler scope enforcement works with OAuth 2.0 tokens, and existing None, API Key, and JWT Token authentication modes remain unchanged.

  • User profile fields in Token Info: The Token Info structure now includes additional standard claims — given_name, family_name, and preferred_username — providing user profile details from the authenticated token for use in downstream flow logic.

• TIBCO Flogo® Connector for TIBCO FTL®: A new Use Certificate for Verification field is added in the FTL connection configuration to enable or disable verification of the FTL server's TLS certificate.

• TIBCO Flogo® Connector for Google Cloud Storage: TIBCO Flogo® Connector for Google Cloud Storage now supports Upload Activity. For more information, see Google Cloud Storage Upload.

• Newly Supported Connector: TIBCO Flogo® Connector for SAP HANA Database is the newly supported connector. For more information, see Supported Flogo Connectors.

For complete release details, see TIBCO Flogo® 2.26.6 Release Notes.