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
Team Memberships → Team Membership Create
AI-generatedOverview
This node allows you to create a new team membership in Portainer by sending the team membership details as a JSON string in the request body. It is useful when you want to programmatically add users or entities to a team within Portainer, automating team management tasks.
Practical examples include:
- Automatically adding new users to specific teams after user creation.
- Managing team memberships in bulk via workflows.
- Integrating team membership updates with other systems or processes.
Properties
| Name | Meaning |
|---|---|
| Body | Team membership details provided as a JSON string. This should contain all necessary information to define the team membership according to Portainer's API requirements. |
Output
The node outputs the response from the Portainer API after creating the team membership. The output is structured as JSON and typically contains details about the newly created team membership, such as its ID and associated properties.
If the API supports binary data in responses (not indicated here), it would be included accordingly, but this node primarily deals with JSON data.
Dependencies
- Requires an API key credential for authenticating with the Portainer API.
- Needs the base URL of the Portainer instance configured in the credentials.
- Depends on the Portainer API being accessible and properly configured to accept team membership creation requests.
Troubleshooting
- Invalid JSON in Body: If the "Body" property contains malformed JSON, the API will reject the request. Ensure the JSON string is correctly formatted.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key and URL are correct.
- API Endpoint Issues: If the Portainer API endpoint is unreachable or returns errors, check network connectivity and API server status.
- Insufficient Permissions: The API user must have permissions to create team memberships; otherwise, the request will fail.
- Error Messages: Common error messages may include HTTP 400 for bad requests (e.g., invalid body), 401 for unauthorized access, or 403 for forbidden actions. Review the error message details to adjust the input or credentials accordingly.
Links and References
- Portainer API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding how API calls are made)
- JSON formatting tools to validate the "Body" input before use