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`.
Version
Provenance
- Empreinte du contenu
- sha256:772818daad76a25f73dd64f4236d7c429dc306ee3f632fe72ab3600c93d08c00
- Publié
- 2026-11-10T10:08:31Z
- 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:28d68fab85eba8f19a937f9f9a3e2554360d27643ca4cedcda9753abcdf15c24
Référence à cette version
oci://hub.aggrega.ai/component/core/ai-agent/n8n: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 |
|---|---|---|---|---|
| workflow_id | string | — | oui | — |
| allow_env_access_in_nodes | boolean | false | non | 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 | — | non | 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 | non | 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. |
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 n8n platform. |
| source_version | string | — | non | 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 | — | non | — |
| external_base_url | string | — | non | 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. |
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>:5678/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
- 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 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
- Sélecteur
- component.aggrega.ai/category=ai-tool, tool.aggrega.ai/transport=http
- 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 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 | non | env | oui | 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
- 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); unattached, no credential is delivered for the store. |
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.
Aucun emplacement d’attache déclaré.
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