Component
core/ai-agent/flowise
The Flowise visual agent-builder, run in-cluster as the image a Release names. Flowise is a browser editor in which a chatflow is assembled from nodes and served over HTTP, so deploying it gives the editor and the endpoint together, backed by a volume holding the chatflow database and the key encrypting the editor's credentials. What this component exposes is the chatflow a caller invokes and the per-request overrides that call may carry; the model wired into the `model` socket arrives as the endpoint an OpenAI-compatible client reads, while the chatflow's own node chooses the model it calls. The catalog pins no image for it: which Flowise build to run is named by the Release, and until that Release sets `infra.image` the build halts naming the container image. A chatflow set as flow_definition is seeded at deploy, on both targets, under the owner account the operator names. Each tool wired into the optional `tools` socket, such as a Model Context Protocol server reached over HTTP, and each vector store wired into the optional `vector_store` socket reach the platform under variables named for the connection's alias, as each socket's comments set out: AGGREGA_TOOL_<ALIAS>_URL or AGGREGA_VECTOR_STORE_<ALIAS>_URL, their parts and the connection's credential, by reference. A chatflow reads each through a Runtime variable of the same name created on Flowise's Variables page, as $vars.<name>; nothing creates one at startup. A connection writing an `inject:` block receives the names it dictates instead of its address and part variables, read the same way; its credentials stay.
Versión
Procedencia
- Digest del contenido
- sha256:9d18b4af783227080c2fa397986a3d0ddb965a15c077a134c8325a7fcebe7e77
- Publicado
- 2026-11-15T08:08:52Z
- Identidad de firma
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Firma
- Oficialapplication/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:10237f0d939cffe91dc82b13a7d7136706cc51a30919a264daee851463e5840b
Referencia en esta versión
oci://hub.aggrega.ai/component/core/ai-agent/flowise:1.1.0Parámetros del desarrollador
Valores que el desarrollador establece en el Aggregate.
Extiende BaseComponents#/schemas/BaseAgentParameter
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| chatflow_id | string | — | sí | — |
| override_config | object | — | no | — |
| flow_definition | string | — | no | A chatflow in the JSON Flowise's editor exports for it, the nodes and edges of the canvas, carried verbatim. Realized by both targets: when set, a one-shot step running the platform's own image seeds it once the platform answers — a Job on helm, carrying the definition in a ConfigMap, and a service that runs once on compose, carrying it in a compose config with every $ written $ and starting once the platform reports healthy. The step registers the owner account named by infra.owner_email with the password attached to the owner_password slot when the instance has no owner yet, and otherwise signs in as that account, halting with the cause when signing in is refused; then it updates the chatflow whose id is chatflow_id, replacing its nodes and edges, or imports the definition at that id where no such chatflow exists, named after display_name or, without one, after chatflow_id. So chatflow_id must be a UUID, which Flowise requires of a chatflow's id, and an edit made to the chatflow's canvas in the editor is replaced the next time the step runs, while its name and settings are kept. When set, infra.owner_email and the owner_password slot are required and the build halts without them. When unset, nothing is seeded and no step is rendered. An Aggregate's text is evaluated as a template before it is read, so a definition carrying Flowise's own {{...}} variable references halts the build when written into an Aggregate as it stands; supply it as a parameter the Release fills, written into this value through toJson, and it arrives as written. |
| metrics_enabled | boolean | false | no | Turns on Flowise's own metrics, in the Prometheus format, at /api/v1/metrics on the platform's port, infra.port, and publishes their address as `metrics_endpoint`; while false that key is empty. Flowise answers them only to a valid Flowise API key presented as a bearer token. |
Dimensionamiento del operador
Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| image | string | — | no | Container image running the Flowise platform. |
| port | integer (min 1024, max 65535) | 3000 | no | HTTP listen port the platform serves the editor and its API on inside its container, and the port of its Service on Kubernetes. |
| published_port | integer (min 1024, max 65535) | — | no | Port 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. |
| storage | object | — | no | — |
| owner_email | string | — | no | Email address of the platform's owner account, read only when values.flow_definition is set. The step that seeds the chatflow registers this account when the instance has no owner yet, which makes it the owner, and signs in as it; on an instance that already has one, it names an account allowed to import chatflows, and the password attached to the owner_password slot is that account's. Required when values.flow_definition is set: the build halts when it is empty. It has no default. |
Contrato de salida
Valores que este componente publica para los consumidores a través de la topología uses.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| metrics_endpoint | string | — | no | The full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:<port>/api/v1/metrics`, the host being the name the platform is served under and the port infra.port. Empty while values.metrics_enabled is false. |
| metrics_credential_required | boolean | — | no | Whether a scrape of `metrics_endpoint` must present a credential: true while values.metrics_enabled is true, because Flowise answers its metrics only to a valid API key, and false while no address is published. The metrics route checks only that the key is valid, and the key opens whatever its permissions allow elsewhere, so create one for the scrape with as little permission as Flowise lets a key carry. |
Sockets uses
Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.
model
- Selector
- component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
- Inyección
- —
Slots que cada conexión a través de este socket puede llenar
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | no | env | sí | 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
- Selector
- component.aggrega.ai/category=ai-tool, tool.aggrega.ai/transport=http
- Inyección
- env, file
Slots que cada conexión a través de este socket puede llenar
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | no | env | sí | Optional credential the platform presents to the tool this connection reaches, under the request header the tool publishes as credential_header: as Bearer <credential> under Authorization, and as the whole value of any other header. When attached, the Recipe delivers it as AGGREGA_TOOL_<ALIAS>_CREDENTIAL (a Kubernetes secretKeyRef on helm, the inject pipe on compose), and, on a connection writing no inject block, the header as AGGREGA_TOOL_<ALIAS>_CREDENTIAL_HEADER where the tool publishes one. |
| endpoint | feature.aggrega.ai/kind=secret | no | env | sí | Optional 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. When attached, the Recipe delivers it as AGGREGA_TOOL_<ALIAS>_URL in place of the endpoint the tool publishes: a Kubernetes secretKeyRef on helm, so the key reaches no rendered file, and the inject pipe on compose, written as delivered. |
vector_store
- Selector
- datastore.aggrega.ai/engine in (vector, semantic-memory, search)
- Inyección
- env, file
Slots que cada conexión a través de este socket puede llenar
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | no | env | sí | 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); unattached, no credential is delivered for the store. |
Slots de acoplamiento
Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| owner_password | feature.aggrega.ai/kind=secret | no | env | sí | Password of the owner account named by infra.owner_email, read only when values.flow_definition is set: the step that seeds the chatflow registers that account with it on a fresh instance, and signs in with it. Required then, and the build halts when nothing fills this slot; there is no development default. On helm the step receives it by reference, as a Kubernetes secretKeyRef to the Secret the credential publishes, so the password appears in no file the Recipe renders, and a credential publishing no Secret name and data key halts the build; on compose it is read from the inject pipe and written as it was delivered, so a Compose variable reference such as ${FLOWISE_OWNER_PASSWORD} lands as that reference. Flowise accepts a password of 8 to 128 characters holding a lower-case and an upper-case letter, a digit and a character that is neither. |
Lista de permitidos de autoinyección
No se declararon canales de autoinyección.
Relaciones
Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.
Usa
- usausa el socket «model»
component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
Slots de acoplamiento: 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 → - usausa el socket «tools»
component.aggrega.ai/category=ai-tool, tool.aggrega.ai/transport=http
Slots de acoplamiento: credential, endpoint
- usausa el socket «vector_store»
datastore.aggrega.ai/engine in (vector, semantic-memory, search)
Slots de acoplamiento: credential
- $refextiende el esquema (values)
BaseComponents#/schemas/BaseAgentParameter
Usado por
usa el socket «runner»
usa el socket «api»
usa el socket «runner»
usa el socket «api»
usa el socket «services»
usa el socket «api»
usa el socket «services»
usa el socket «services»
usa el socket «sandbox»
usa el socket «plugin_daemon»
usa el socket «ssrf_proxy»
usa el socket «sandbox»
usa el socket «plugin_daemon»
usa el socket «ssrf_proxy»
usa el socket «api»
usa el socket «ssrf_proxy»
usa el socket «api»
usa el socket «api»
usa el socket «sandbox»
usa el socket «plugin_daemon»
usa el socket «ssrf_proxy»
usa el socket «sandbox»
usa el socket «plugin_daemon»
usa el socket «ssrf_proxy»
usa el socket «target_agent»
usa el socket «upstream»
usa el socket «forward_target»
usa el socket «scrape_target»
usa el socket «store»
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
implementa
implementa