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
- 서명 ID
- 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가 슬롯을 채울 수 있는지를 제한하고, 슬롯의 inject 목록은 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» 사용
적용 대상
적용 대상
적용 대상
적용 대상
적용 대상
적용 대상
적용 대상
구현
구현