Component
core/ai-agent/n8n
The n8n automation platform, run in-cluster as the image a Release names. n8n runs workflows built from connected nodes and started by a webhook, a schedule or an event, so deploying it gives the editor and the webhook endpoint together, with a model reachable from whichever node needs one. What this component exposes is the workflow a caller invokes and, optionally, the workflow definition itself: supplied in the Aggregate, it is imported before the platform starts and on every start, so the platform runs the workflow as authored, whatever its data directory holds. The catalog pins no image: the Release names it in `infra.image`, and the build halts naming the container image until it does. The model, and each tool and store wired into the optional `tools` and `vector_store` sockets, reach the platform as environment variables, each credential by reference; each socket's comments and slots name them. A connection writing an `inject:` block receives the names it dictates instead of those its target's values fill; its credentials stay. A workflow reads these through n8n's $env only where the Aggregate sets `values.allow_env_access_in_nodes` to true. By default the Recipes keep n8n's block on environment access in expressions and the Code node, and lifting it lets every workflow read every variable of the platform's environment, the delivered credentials included. On Kubernetes, reach for `n8n-chart`, rendering n8n's own chart, where a chart repository is reachable at build time, and for `n8n`, the workload synthesis, where the build must fetch nothing. Of the two, only `n8n-chart` keeps the data directory on a volume that survives a restart, sized by `infra.storage.size`.
Sürüm
Köken
- İçerik özeti
- sha256:9e50d98c38df38057cc90e396def59e51993ea59eaa983d23c45a71e684e8b0b
- Yayımlanma
- 2026-11-15T08:08:55Z
- İmzalama kimliği
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
İmza
- Resmiapplication/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:2050079cb4b6e7b8c29405a6b754797e33d3f58b1b45f0cf4fccf51b20b4f541
Bu sürümdeki referans
oci://hub.aggrega.ai/component/core/ai-agent/n8n:1.1.0Geliştirici parametreleri
Geliştiricinin Aggregate'te ayarladığı değerler.
BaseComponents#/schemas/BaseAgentParameter öğesini genişletir
| Ad | Tip | Varsayılan | Zorunlu | Açıklama |
|---|---|---|---|---|
| workflow_id | string | — | evet | — |
| allow_env_access_in_nodes | boolean | false | hayır | Whether workflows may read the platform's environment through n8n's $env, in expressions and the Code node. While false, its default, the Recipes deliver N8N_BLOCK_ENV_ACCESS_IN_NODE set to true, n8n refuses every such read, and the delivered model, tool and store values cannot be read by a workflow. Set true, the variable is delivered as false, and every workflow, and every user who can edit one, can read every variable of the platform's environment, the delivered credentials included. |
| flow_definition | string | — | hayır | The n8n workflow definition (JSON) the developer authors. Both targets realize it with an init step that imports the definition before the platform starts: the helm target carries it in a ConfigMap, and the compose target carries it in a config. An Aggregate's text is evaluated as a template before it is read, so a definition carrying n8n's own {{ ... }} expressions 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, no init step is rendered and the platform deploys with no seeded workflow — author or import the workflow through the editor instead. |
| metrics_enabled | boolean | false | hayır | Turns on n8n's own metrics, in the Prometheus format, and publishes their address as `metrics_endpoint`; while false that key is empty. They are served at /metrics on the platform's main port, which answers that path without a sign-in, so anything that reaches the port can read them. |
Operatör boyutlandırması
Operatörün her ortam için ayarladığı altyapı boyutlandırması.
| Ad | Tip | Varsayılan | Zorunlu | Açıklama |
|---|---|---|---|---|
| image | string | — | hayır | Container image running the n8n platform. |
| port | integer (min 1024, max 65535) | 5678 | hayır | Port n8n listens on inside its container, serving the editor and the webhook endpoint, and the port of its Service on Kubernetes. On Docker Compose, where infra.published_port differs from it, set infra.external_base_url to http://127.0.0.1:<published_port> so the addresses n8n shows name the published port. |
| published_port | integer (min 1024, max 65535) | — | hayır | 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. |
| source_version | string | — | hayır | Version of n8n's own Helm chart the chart-backed Recipe pulls, defaulting to the version that Recipe was checked against. The workload-synthesis and compose Recipes pull no chart and read nothing here. |
| storage | object | — | hayır | — |
| external_base_url | string | — | hayır | Externally reachable base URL of the platform, as assembled at the ingress tier — for example https://n8n.example.com. The platform composes from this the editor address it puts in the emails it sends and hands a SAML identity provider to return a browser to, and the base of every webhook URL it shows in the editor and registers with an outside service, so a service calling a workflow back reaches the platform. The editor is served from the root of that address; the product recommends a host of its own over a path behind a reverse proxy. Omitted, the Recipes set neither address and the platform composes both from its host, port and path settings, whose defaults name localhost — correct only for a platform no outside service calls. |
Çıktı sözleşmesi
Bu bileşenin uses topolojisi üzerinden tüketicilere yayımladığı değerler.
| Ad | Tip | Varsayılan | Zorunlu | Açıklama |
|---|---|---|---|---|
| metrics_endpoint | string | — | hayır | The full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:<port>/metrics`, the host being the platform's Service name and the port `infra.port`, 5678 unless the Release sets another. Empty while values.metrics_enabled is false. |
Uses soketleri
Bu bileşenin üzerinden bağlandığı bağımlılık soketleri. Bir soket üzerinden kurulan her bağlantının hedefi, soketin etiket seçicisini karşılamalıdır ve her bağlantı, soketin bildirdiği yuvalarda bir ek taşıyabilir. Aggregate'in veya Release'in soket üzerinden kurduğu her bağlantı, zorunlu bir yuvayı doldurmakla yükümlüdür.
model
- Seçici
- component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
- Enjeksiyon
- env, file
Bu soket üzerinden kurulan her bağlantının doldurabileceği yuvalar
| Yuva | Seçici | Zorunlu | Enjeksiyon | Hassas | Açıklama |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | hayır | env | evet | 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), which a workflow reads through n8n's $env only while allow_env_access_in_nodes is true, the Recipes otherwise keeping n8n's block on environment access in nodes; unattached, the platform runs without an injected key. |
tools
- Seçici
- component.aggrega.ai/category=ai-tool, tool.aggrega.ai/transport=http
- Enjeksiyon
- env, file
Bu soket üzerinden kurulan her bağlantının doldurabileceği yuvalar
| Yuva | Seçici | Zorunlu | Enjeksiyon | Hassas | Açıklama |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | hayır | env | evet | 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 | hayır | env | evet | 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
- Seçici
- datastore.aggrega.ai/engine in (vector, semantic-memory, search)
- Enjeksiyon
- env, file
Bu soket üzerinden kurulan her bağlantının doldurabileceği yuvalar
| Yuva | Seçici | Zorunlu | Enjeksiyon | Hassas | Açıklama |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | hayır | env | evet | 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. |
Ekleme yuvaları
Bir Feature'ın bu bileşene eklendiği adlandırılmış bağlama noktaları. Bir yuvanın seçicisi, onu hangi Feature'ın doldurabileceğini sınırlar ve inject listesi, Feature'ın malzemesinin nasıl iletilebileceğini belirtir. Zorunlu bir yuva, her örnekte, örnek üzerindeki veya onun üstündeki bir kapsamdaki bir ek aracılığıyla bağlanmalıdır, hassas bir yuva ise gizli malzemeyi işlemek üzere bildirilmiştir. Bir Feature, hiçbir yuvanın bildirmediği bir ad altında da eklenebilir.
Ekleme yuvası bildirilmemiş.
Kendi kendine enjeksiyon izin listesi
Kendi kendine enjeksiyon kanalı bildirilmemiş.
İlişkiler
Diğer yayımlanmış varlıklara giden ve onlardan gelen tipli kenarlar. Yayımlanmış bir hedefi olmayan bir başvuru, bağlantı yerine kopuk bir kenar olarak gösterilir.
Kullanır
- kullanır«model» soketini kullanır
component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
Ekleme yuvaları: 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 → - kullanır«tools» soketini kullanır
component.aggrega.ai/category=ai-tool, tool.aggrega.ai/transport=http
Ekleme yuvaları: credential, endpoint
- kullanır«vector_store» soketini kullanır
datastore.aggrega.ai/engine in (vector, semantic-memory, search)
Ekleme yuvaları: credential
- $refşemayı genişletir (values)
BaseComponents#/schemas/BaseAgentParameter
Kullananlar
«runner» soketini kullanır
«api» soketini kullanır
«runner» soketini kullanır
«api» soketini kullanır
«services» soketini kullanır
«api» soketini kullanır
«services» soketini kullanır
«services» soketini kullanır
«sandbox» soketini kullanır
«plugin_daemon» soketini kullanır
«ssrf_proxy» soketini kullanır
«sandbox» soketini kullanır
«plugin_daemon» soketini kullanır
«ssrf_proxy» soketini kullanır
«api» soketini kullanır
«ssrf_proxy» soketini kullanır
«api» soketini kullanır
«api» soketini kullanır
«sandbox» soketini kullanır
«plugin_daemon» soketini kullanır
«ssrf_proxy» soketini kullanır
«sandbox» soketini kullanır
«plugin_daemon» soketini kullanır
«ssrf_proxy» soketini kullanır
«target_agent» soketini kullanır
«upstream» soketini kullanır
«forward_target» soketini kullanır
«scrape_target» soketini kullanır
«store» soketini kullanır
uygulanır
uygulanır
uygulanır
uygulanır
uygulanır
uygulanır
uygulanır
uygular
uygular
uygular