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
Custom Templates → Custom Template Create Repository
AI-generatedOverview
This node operation, Custom Template Create Repository, allows users to create a new repository using a custom template within the Portainer environment. It is useful for automating the creation of repositories based on predefined templates, which can streamline deployment workflows and ensure consistency across projects.
Typical use cases include:
- Automating repository setup in container management or DevOps pipelines.
- Creating standardized project repositories with predefined configurations.
- Integrating repository creation into larger automation workflows in n8n.
Properties
| Name | Meaning |
|---|---|
| Body | The JSON string body containing the details required to create the repository. This is mandatory when performing the repository creation operation. The content should conform to the API's expected schema for repository creation. |
Output
The node outputs JSON data representing the response from the Portainer API after attempting to create the repository. This typically includes information about the newly created repository such as its ID, name, status, and any relevant metadata returned by the API.
If the API supports binary data output (not indicated here), it would be summarized accordingly, but this operation primarily deals with JSON responses.
Dependencies
- Requires an active connection to a Portainer instance via its API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for the Portainer API must be set correctly in the node credentials.
Troubleshooting
- Invalid or missing body: Since the "Body" property is required, omitting it or providing malformed JSON will cause errors. Ensure the JSON string is valid and matches the API schema.
- Authentication errors: If the API key or token is incorrect or expired, the node will fail to authenticate. Verify credentials and permissions.
- API endpoint issues: Incorrect base URL or network connectivity problems can prevent successful API calls. Confirm the Portainer URL and network access.
- Unexpected API responses: If the API changes or returns errors, check the response message for clues and update the request body accordingly.
Links and References
- Portainer API Documentation
- n8n Documentation - HTTP Request Node (for understanding API interactions)
- JSON Schema Validator (to validate the "Body" JSON input)