Component

core/ai-agent/langflow

The Langflow visual flow-builder, run in-cluster as the image a Release names. Deploying it gives the browser editor and the endpoint serving its flows, on a volume holding them and their encryption key. This component exposes the flow a caller invokes, the per-request tweaks that call may carry, and how the editor is reached: signing in is required by default, so the seeded administrator's password is attached or the build halts, while an Aggregate wanting the editor open to anyone says so. A flow authored in the Aggregate is loaded at each start on both targets, which an image at Langflow 1.5.1 or older does only with signing in off. The catalog pins no image: the Release names it in `infra.image`, and the build halts until it does. Each vector store wired into the optional `vector_store` socket arrives under variables named for the connection's alias: its address as AGGREGA_VECTOR_STORE_<ALIAS>_URL, and the connection's credential as AGGREGA_VECTOR_STORE_<ALIAS>_CREDENTIAL. A connection writing an `inject:` block receives the names it dictates instead, read by a flow as global variables; its credential stays. Each tool wired into the optional `tools` socket, a Model Context Protocol server reached over HTTP, is written into the flow's MCP Tools node named for the connection's alias. With `values.metrics_enabled` true Langflow's metrics are served at /metrics on port 9090, which checks no caller, and published as `metrics_endpoint`. On Kubernetes, reach for `langflow`, the workload synthesis, where the build must fetch nothing or the metrics are wanted, and for `langflow-chart`, rendering Langflow's own chart, which refuses them, where a chart repository is reachable at build time.

Version

1.0.01.1.0

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:6f5536c692151757234183dc385c70ae6ac1104f1f0d9322495cfff26b04c90d
Published
2026-11-15T08:08:55Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:1f0d160b6acc37733290193b87c805adead3de09e7ebf7117e12bfc21a63a5a8

Reference at this version

oci://hub.aggrega.ai/component/core/ai-agent/langflow:1.1.0

Developer parameters

Values the developer sets in the Aggregate.

Extends BaseComponents#/schemas/BaseAgentParameter

NameTypeDefaultRequiredDescription
flow_idstring—yes—
flow_definitionstring—noA Langflow flow definition (JSON) the developer authors, realized on both targets: the helm target carries it in a ConfigMap mounted as the directory LANGFLOW_LOAD_FLOWS_PATH names, and the compose target in a compose config mounted as one file in that directory, every $ written as $ so Docker Compose delivers it unchanged. Langflow loads the directory into the administrator's flows at each start, whether or not signing in is required; where the definition carries the id of a flow already loaded, that flow is updated in place, so an edit made to it in the editor is replaced at the next start. An image at Langflow 1.5.1 or older loads it only with require_authentication false. Where tools connections are wired, each MCP Tools node whose server is named for a connection's alias has that connection's address, and the header carrying its credential, written into the node's server configuration, every other part of the definition kept and the whole written back as JSON with its keys sorted; with no tools connection the definition is carried as written. A node naming a server no tools connection answers halts the build, as does a tools connection no node names, a node it names that starts a server of its own, and a tools connection wired with no definition. A server of the same name stored in Langflow's settings takes precedence over the configuration written here. An Aggregate's text is evaluated as a template before it is read, so a definition whose component source carries {{ halts the build when written into an Aggregate as it stands; write each {{ in it as {{"{{"}}, and interpolation restores the definition's text. When unset, the platform deploys with no seeded flow.
tweaksobject—no—
require_authenticationbooleantruenoWhether reaching the editor requires signing in. At the default the platform's built-in sign-in bypass is switched off and the seeded administrator account is the only way in, so that account's password must be attached to the admin_password slot; leaving this at the default and attaching nothing is refused at build rather than deployed with an editor nobody can sign in to. Set it to false to run the editor with the bypass on, where everyone who can reach the service arrives already signed in as the administrator and no credential is needed.
admin_userstringadminnoLogin name of the administrator account the platform seeds at startup. Read only where the editor requires a sign-in; with require_authentication false no account is seeded and nothing reads this value.
metrics_enabledbooleanfalsenoTurns on Langflow's own metrics, in the Prometheus format, on a port of their own, 9090, and publishes their address as `metrics_endpoint`; while false that key is empty. The metrics port checks no caller, so anything that reaches it can read them. The langflow-chart Recipe refuses true, since the chart it renders has no Service port for the metrics; the workload-synthesis and compose Recipes serve them.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
imagestring—noContainer image running the Langflow platform.
source_versionstring—noVersion of Langflow's own langflow-ide Helm chart the chart-backed Recipe pulls, defaulting to the version that Recipe was checked against. The workload-synthesis Recipe pulls no chart and reads nothing here.
storageobject—no—
portinteger (min 1024, max 65535)7860noHTTP listen port the platform serves the editor and its flows' endpoint on inside its container, and the port of its Service on Kubernetes.
published_portinteger (min 1024, max 65535)—noPort published on the host's loopback address, 127.0.0.1, on Docker Compose, forwarding to infra.port inside the container; any process on this machine can reach it there. Unset, nothing is published. Kubernetes realizations refuse it; reach the Service with kubectl port-forward, or attach core/public-ingress.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
metrics_endpointstring—noThe full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:9090/metrics`, the host being the platform's Service name. Empty while values.metrics_enabled is false.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

model

Selector
component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
Inject
—

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credentialfeature.aggrega.ai/kind=secretnoenvyesOptional credential the platform presents to the model this connection reaches. When attached, the Recipe delivers it to the platform as OPENAI_API_KEY (a Kubernetes secretKeyRef on helm, the inject pipe on compose); unattached, the platform runs without an injected key.

tools

Selector
component.aggrega.ai/category=ai-tool, tool.aggrega.ai/transport=http
Inject
—

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credentialfeature.aggrega.ai/kind=secretnoenvyesOptional credential the platform presents to the tool this connection reaches, under the request header the tool publishes as credential_header. When attached, the Recipe delivers it as AGGREGA_TOOL_<ALIAS>_CREDENTIAL (a Kubernetes secretKeyRef on helm, the inject pipe on compose), has Langflow store as a global variable the variable holding the header's whole value, and writes that variable's name as the header's value in the MCP Tools node the connection reaches, so the credential is written into no rendered flow. Under any header but Authorization that variable is AGGREGA_TOOL_<ALIAS>_CREDENTIAL itself. Under Authorization, which takes Bearer <credential> as its value, it is AGGREGA_TOOL_<ALIAS>_AUTHORIZATION, holding Bearer and the credential: on helm a reference Kubernetes expands from the delivered Secret when the container starts, on compose the credential as delivered. Langflow stores the variable for the administrator at each sign-in, or, with require_authentication false, once when it creates the administrator, so until then the header carries the variable's name. The build halts where the tool publishes no header to present a credential under.
endpointfeature.aggrega.ai/kind=secretnoenvyesThe whole address of the tool this connection reaches, the part carrying its key included, for a server that reads its key from its own address. Langflow reads an MCP server's address only from the flow file it loads, where that key would be written as a literal, so an attachment here halts the build naming the connection, on both targets.

vector_store

Selector
datastore.aggrega.ai/engine in (vector, semantic-memory, search)
Inject
env, file

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credentialfeature.aggrega.ai/kind=secretnoenvyesOptional credential the platform presents to the vector store this connection reaches, such as the API key the store checks. When attached, the Recipe delivers it as AGGREGA_VECTOR_STORE_<ALIAS>_CREDENTIAL (a Kubernetes secretKeyRef on helm, the inject pipe on compose), and, for a store publishing a database and a user, as the password inside AGGREGA_VECTOR_STORE_<ALIAS>_CONNECTION_STRING, written unencoded; unattached, no credential is delivered for the store and that string carries no password.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

SlotSelectorRequiredInjectSensitiveDescription
admin_passwordfeature.aggrega.ai/kind=secretnoenvyesPassword of the administrator account the platform seeds at startup, delivered as LANGFLOW_SUPERUSER_PASSWORD (a Kubernetes secretKeyRef on helm, the inject pipe on compose). Attach it wherever require_authentication is left at its default, since that account is then the only way into the editor; with require_authentication false the platform signs every visitor in and nothing reads this slot.

Self-inject allowlist

No self-inject pipes declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy