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.
Версия
Происхождение
- Дайджест содержимого
- sha256:7b7804901755991cc8e7cbb07523825b9daa0f8551aca6946e734cfcd0475afd
- Опубликовано
- 2026-11-10T10:08:02Z
- Идентичность подписи
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Подпись
- Официальныйapplication/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:731f0138a1b827931b84bac8a4f313f2be9cb481019dc0bf3a85c1ce050da553
Ссылка на эту версию
oci://hub.aggrega.ai/component/core/ai-agent/flowise:1.0.0Параметры разработчика
Значения, которые разработчик задаёт в сущности Aggregate.
Расширяет BaseComponents#/schemas/BaseAgentParameter
| Имя | Тип | По умолчанию | Обязательный | Описание |
|---|---|---|---|---|
| chatflow_id | string | — | да | — |
| override_config | object | — | нет | — |
| flow_definition | string | — | нет | 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 | нет | Turns on Flowise's own metrics, in the Prometheus format, at /api/v1/metrics on the platform's port, 3000, 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. |
Размеры, задаваемые оператором
Размеры инфраструктуры, которые оператор настраивает для каждого окружения.
| Имя | Тип | По умолчанию | Обязательный | Описание |
|---|---|---|---|---|
| image | string | — | нет | Container image running the Flowise platform. |
| storage | object | — | нет | — |
| owner_email | string | — | нет | 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. |
Контракт выходных значений
Значения, которые этот компонент публикует для потребителей через топологию uses.
| Имя | Тип | По умолчанию | Обязательный | Описание |
|---|---|---|---|---|
| metrics_endpoint | string | — | нет | The full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:3000/api/v1/metrics`, the host being the name the platform is served under. Empty while values.metrics_enabled is false. |
| metrics_credential_required | boolean | — | нет | 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. |
Сокеты uses
Сокеты зависимостей, через которые подключается этот компонент. Цель каждого соединения, проведённого через сокет, должна удовлетворять его селектору меток, и каждое соединение может нести подключение в слотах, которые объявляет сокет. Обязательный слот должен заполнить каждое соединение, которое сущность Aggregate или сущность Release проводит через сокет.
model
- Селектор
- component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
- Внедрение
- —
Слоты, которые может заполнить каждое соединение через этот сокет
| Слот | Селектор | Обязательный | Внедрение | Конфиденциальный | Описание |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | нет | env | да | 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
- Селектор
- component.aggrega.ai/category=ai-tool, tool.aggrega.ai/transport=http
- Внедрение
- env, file
Слоты, которые может заполнить каждое соединение через этот сокет
| Слот | Селектор | Обязательный | Внедрение | Конфиденциальный | Описание |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | нет | env | да | 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 | нет | env | да | 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
- Селектор
- datastore.aggrega.ai/engine in (vector, semantic-memory, search)
- Внедрение
- env, file
Слоты, которые может заполнить каждое соединение через этот сокет
| Слот | Селектор | Обязательный | Внедрение | Конфиденциальный | Описание |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | нет | env | да | 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. |
Слоты подключения
Именованные точки привязки, в которых Feature подключается к этому компоненту. Селектор слота ограничивает, какая сущность Feature может его заполнить, а его список внедрения указывает, как могут доставляться материалы сущности Feature. Обязательный слот должен быть привязан в каждом экземпляре — подключением в самом экземпляре или в области выше него, — а конфиденциальный слот объявляется для работы с секретными материалами. Feature также может подключаться под именем, которое не объявляет ни один слот.
| Слот | Селектор | Обязательный | Внедрение | Конфиденциальный | Описание |
|---|---|---|---|---|---|
| owner_password | feature.aggrega.ai/kind=secret | нет | env | да | 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. |
Список разрешённых самовнедрений
Каналы самовнедрения не объявлены.
Связи
Типизированные рёбра к другим опубликованным сущностям и от них. Ссылка без опубликованной цели отображается как разорванное ребро, а не как ссылка.
Использует
- используетиспользует сокет «model»
component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
Слоты подключения: 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 → - используетиспользует сокет «tools»
component.aggrega.ai/category=ai-tool, tool.aggrega.ai/transport=http
Слоты подключения: credential, endpoint
- используетиспользует сокет «vector_store»
datastore.aggrega.ai/engine in (vector, semantic-memory, search)
Слоты подключения: credential
- $refрасширяет схему (values)
BaseComponents#/schemas/BaseAgentParameter
Используется в
использует сокет «runner»
использует сокет «api»
использует сокет «runner»
использует сокет «api»
использует сокет «services»
использует сокет «api»
использует сокет «services»
использует сокет «services»
использует сокет «sandbox»
использует сокет «plugin_daemon»
использует сокет «ssrf_proxy»
использует сокет «sandbox»
использует сокет «plugin_daemon»
использует сокет «ssrf_proxy»
использует сокет «api»
использует сокет «ssrf_proxy»
использует сокет «api»
использует сокет «api»
использует сокет «sandbox»
использует сокет «plugin_daemon»
использует сокет «ssrf_proxy»
использует сокет «sandbox»
использует сокет «plugin_daemon»
использует сокет «ssrf_proxy»
использует сокет «target_agent»
использует сокет «upstream»
использует сокет «forward_target»
использует сокет «scrape_target»
использует сокет «store»
применяется к
применяется к
применяется к
применяется к
применяется к
применяется к
применяется к
реализует
реализует