Actions190
- Auth Actions
- Backup Actions
- Custom Templates Actions
- Docker Actions
- Edge Groups Actions
- Edge Jobs Actions
- Edge Stacks Actions
- Endpoint Groups Actions
- Endpoints Actions
- Endpoint Delete Batch
- Endpoint List
- Endpoint Create
- Endpoint Delete
- Endpoint Inspect
- Endpoint Update
- Endpoint Association Delete
- Endpoint Dockerhub Status
- Endpoint Edge Status Inspect
- Endpoint Force Update Service
- Endpoint Registries List
- Endpoint Registry Access
- Endpoint Settings Update
- Endpoint Snapshot
- Endpoint Update Relations
- Gitops Actions
- Helm Actions
- Intel Actions
- Kubernetes Actions
- Get All Kubernetes Applications
- Get All Kubernetes Applications Count
- Delete Cluster Role Bindings
- Delete Cluster Roles
- Get All Kubernetes Cluster Role Bindings
- Get All Kubernetes Cluster Roles
- Get All Kubernetes Config Maps
- Get All Kubernetes Config Maps Count
- Get Kubernetes Cron Jobs
- Delete Cron Jobs
- Get Kubernetes Dashboard
- Get All Kubernetes Ingress Controllers
- Update Kubernetes Ingress Controllers
- Get All Kubernetes Cluster Ingresses
- Get All Kubernetes Cluster Ingresses Count
- Delete Kubernetes Ingresses
- Get Kubernetes Jobs
- Delete Jobs
- Get Kubernetes Max Resource Limits
- Get Applications Resources
- Get Kubernetes Metrics For All Nodes
- Get Kubernetes Metrics For Node
- Get Kubernetes Metrics For All Pods
- Get Kubernetes Metrics For Pod
- Delete Kubernetes Namespace
- Get Kubernetes Namespaces
- Create Kubernetes Namespace
- Update Kubernetes Namespace Deprecated
- Get Kubernetes Namespace
- Update Kubernetes Namespace
- Get Kubernetes Config Map
- Get Kubernetes Ingress Controllers By Namespace
- Update Kubernetes Ingress Controllers By Namespace
- Get All Kubernetes Ingresses
- Create Kubernetes Ingress
- Update Kubernetes Ingress
- Get Kubernetes Ingress
- Get Kubernetes Secret
- Get Kubernetes Services By Namespace
- Create Kubernetes Service
- Update Kubernetes Service
- Kubernetes Namespaces Toggle System
- Get Kubernetes Volumes In Namespace
- Get Kubernetes Namespaces Count
- Get Kubernetes Nodes Limits
- Get Kubernetes RBAC Status
- Delete Role Bindings
- Get Kubernetes Role Bindings
- Get Kubernetes Roles
- Delete Roles
- Get Kubernetes Secrets
- Get Kubernetes Secrets Count
- Delete Service Accounts
- Get Kubernetes Service Accounts
- Get Kubernetes Services
- Get All Kubernetes Services Count
- Delete Kubernetes Services
- Get All Kubernetes Volumes
- Get Kubernetes Volume
- Get All Kubernetes Volumes Count
- Get Kubernetes Config
- Ldap Actions
- Registries Actions
- Resource Controls Actions
- Settings Actions
- Ssl Actions
- Stacks Actions
- Stack List
- Stack Delete
- Stack Inspect
- Stack Update
- Stack Associate
- Stack File Inspect
- Stack Update Git
- Stack Git Redeploy
- Stack Migrate
- Stack Start
- Stack Stop
- Stack Create Kubernetes Git
- Stack Create Kubernetes File
- Stack Create Kubernetes Url
- Stack Create Docker Standalone File
- Stack Create Docker Standalone Repository
- Stack Create Docker Standalone String
- Stack Create Docker Swarm File
- Stack Create Docker Swarm Repository
- Stack Create Docker Swarm String
- Stack Delete Kubernetes By Name
- Webhook Invoke
- Tags Actions
- Team Memberships Actions
- Teams Actions
- Templates Actions
- Upload Actions
- Users Actions
Helm → Helm User Repository Create
AI-generatedOverview
This node operation allows creating a Helm user repository by sending a specified payload to the Helm service. It is useful in scenarios where you want to programmatically add or register a new Helm repository for a user, such as automating deployment pipelines or managing Helm repositories within Kubernetes environments.
For example, you might use this node to create a new Helm chart repository for a developer team, enabling them to deploy charts from that repository via Helm commands.
Properties
| Name | Meaning |
|---|---|
| Id | User identifier (a numeric ID) |
| Payload | Helm Repository data as a string (the repository details to create) |
Output
The node outputs JSON data representing the response from the Helm service after attempting to create the user repository. This typically includes confirmation of creation, repository details, or error information if the creation failed.
No binary data output is indicated.
Dependencies
- Requires an API key credential to authenticate with the Helm service.
- The node expects the Helm service URL and authentication credentials to be configured in n8n.
- The request is sent as a JSON body containing the repository payload.
Troubleshooting
Common issues:
- Invalid or missing user identifier (
Id) will cause the request to fail. - Malformed or incomplete
Payloadmay result in errors from the Helm API. - Authentication failures due to incorrect or missing API credentials.
- Network connectivity issues to the Helm service endpoint.
- Invalid or missing user identifier (
Error messages:
- Errors returned from the Helm API will be passed through; check the message for details on invalid input or permission issues.
- If the node fails to connect, verify the base URL and credentials configuration.
Links and References
- Helm Official Documentation
- Helm Repositories
- n8n documentation on HTTP Request Node (for understanding how API calls are made)