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
Provenance
- Empreinte du contenu
- sha256:3903e567dc871d167708fe33f309d7560959fd92d2258e3685a7b179b7baf1d0
- Publié
- 2026-11-10T10:08:13Z
- Identité de signature
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signature
- Officielapplication/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:fcee870dbce0969a72d4187dec219f78234be7a5ed9cbbcf640c99645f8d0719
Référence à cette version
oci://hub.aggrega.ai/component/core/ai-agent/langflow:1.0.0Paramètres du développeur
Valeurs que le développeur définit dans l’Aggregate.
Étend BaseComponents#/schemas/BaseAgentParameter
| Nom | Type | Valeur par défaut | Obligatoire | Description |
|---|---|---|---|---|
| flow_id | string | — | oui | — |
| flow_definition | string | — | non | A 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. |
| tweaks | object | — | non | — |
| require_authentication | boolean | true | non | Whether 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_user | string | admin | non | Login 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_enabled | boolean | false | non | Turns 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. |
Dimensionnement de l’opérateur
Dimensionnement de l’infrastructure que l’opérateur ajuste pour chaque environnement.
| Nom | Type | Valeur par défaut | Obligatoire | Description |
|---|---|---|---|---|
| image | string | — | non | Container image running the Langflow platform. |
| source_version | string | — | non | Version 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. |
| storage | object | — | non | — |
Contrat de sortie
Valeurs que ce composant publie vers les consommateurs via la topologie uses.
| Nom | Type | Valeur par défaut | Obligatoire | Description |
|---|---|---|---|---|
| metrics_endpoint | string | — | non | The 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. |
Sockets uses
Les sockets de dépendance par lesquels ce composant se connecte. La cible de chaque connexion câblée via un socket doit satisfaire son sélecteur d’étiquettes, et chaque connexion peut porter une attache dans les emplacements que le socket déclare. Un emplacement obligatoire doit être rempli par chaque connexion que l’Aggregate ou la Release câble via le socket.
model
- Sélecteur
- component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
- Injection
- —
Emplacements que chaque connexion passant par ce socket peut remplir
| Emplacement | Sélecteur | Obligatoire | Injection | Sensible | Description |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | non | env | oui | Optional 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
- Sélecteur
- component.aggrega.ai/category=ai-tool, tool.aggrega.ai/transport=http
- Injection
- —
Emplacements que chaque connexion passant par ce socket peut remplir
| Emplacement | Sélecteur | Obligatoire | Injection | Sensible | Description |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | non | env | oui | Optional 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. |
| endpoint | feature.aggrega.ai/kind=secret | non | env | oui | The 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
- Sélecteur
- datastore.aggrega.ai/engine in (vector, semantic-memory, search)
- Injection
- env, file
Emplacements que chaque connexion passant par ce socket peut remplir
| Emplacement | Sélecteur | Obligatoire | Injection | Sensible | Description |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | non | env | oui | Optional 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. |
Emplacements d’attache
Points de liaison nommés auxquels une Feature s’attache à ce composant. Le sélecteur d’un emplacement restreint la Feature qui peut le remplir, et sa liste inject indique comment le matériel de la Feature peut être livré. Un emplacement obligatoire doit être lié sur chaque instance, par une attache sur l’instance ou à une portée supérieure, et un emplacement sensible est déclaré pour traiter du matériel secret. Une Feature peut aussi s’attacher sous un nom qu’aucun emplacement ne déclare.
| Emplacement | Sélecteur | Obligatoire | Injection | Sensible | Description |
|---|---|---|---|---|---|
| admin_password | feature.aggrega.ai/kind=secret | non | env | oui | Password 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. |
Liste d’autorisation d’auto-injection
Aucun canal d’auto-injection déclaré.
Relations
Arêtes typées vers et depuis d’autres entités publiées. Une référence sans cible publiée s’affiche comme une arête rompue plutôt que comme un lien.
Utilise
- utiliseutilise le socket « model »
component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
Emplacements d’attache : credential
core/ai-model/ai21 v1.0.0 →core/ai-model/anthropic v1.0.0 →core/ai-model/azure-managed v1.0.0 →core/ai-model/azure-openai v1.0.0 →core/ai-model/azure-openai-embedding v1.0.0 →core/ai-model/bedrock v1.0.0 →core/ai-model/bedrock-embedding v1.0.0 →core/ai-model/cohere v1.0.0 →core/ai-model/databricks v1.0.0 →core/ai-model/docker-model-runner v1.0.0 →core/ai-model/gemini v1.0.0 →core/ai-model/huggingface v1.0.0 →core/ai-model/litellm v1.0.0 →core/ai-model/mistral v1.0.0 →core/ai-model/nvidia-api v1.0.0 →core/ai-model/nvidia-nim v1.0.0 →core/ai-model/ollama v1.0.0 →core/ai-model/openai v1.0.0 →core/ai-model/openai-compatible v1.0.0 →core/ai-model/openai-embedding v1.0.0 →core/ai-model/replicate v1.0.0 →core/ai-model/sagemaker v1.0.0 →core/ai-model/tei v1.0.0 →core/ai-model/tgi v1.0.0 →core/ai-model/vertex-ai v1.0.0 →core/ai-model/vertex-ai-embedding v1.0.0 →core/ai-model/vllm v1.0.0 →core/gateway/agentgateway v1.0.0 →core/gateway/apisix v1.0.0 →core/gateway/envoy-gateway v1.0.0 →core/gateway/higress v1.0.0 →core/gateway/kong v1.0.0 →core/gateway/kong-enterprise v1.0.0 →core/gateway/litellm v1.0.0 →core/gateway/traefik-hub v1.0.0 → - utiliseutilise le socket « tools »
component.aggrega.ai/category=ai-tool, tool.aggrega.ai/transport=http
Emplacements d’attache : credential, endpoint
- utiliseutilise le socket « vector_store »
datastore.aggrega.ai/engine in (vector, semantic-memory, search)
Emplacements d’attache : credential
- $refétend le schéma (values)
BaseComponents#/schemas/BaseAgentParameter
Utilisé par
utilise le socket « runner »
utilise le socket « api »
utilise le socket « runner »
utilise le socket « api »
utilise le socket « services »
utilise le socket « api »
utilise le socket « services »
utilise le socket « services »
utilise le socket « sandbox »
utilise le socket « plugin_daemon »
utilise le socket « ssrf_proxy »
utilise le socket « sandbox »
utilise le socket « plugin_daemon »
utilise le socket « ssrf_proxy »
utilise le socket « api »
utilise le socket « ssrf_proxy »
utilise le socket « api »
utilise le socket « api »
utilise le socket « sandbox »
utilise le socket « plugin_daemon »
utilise le socket « ssrf_proxy »
utilise le socket « sandbox »
utilise le socket « plugin_daemon »
utilise le socket « ssrf_proxy »
utilise le socket « target_agent »
utilise le socket « upstream »
utilise le socket « forward_target »
utilise le socket « scrape_target »
utilise le socket « store »
s’applique à
s’applique à
s’applique à
s’applique à
s’applique à
s’applique à
s’applique à
implémente
implémente
implémente