Actions72
- Image Actions
- Network Actions
- Node Actions
- Registry Actions
- Secret Actions
- Service Actions
- Stack Actions
- Team Actions
- Template Actions
- User Actions
- Volume Actions
- Webhook Actions
- Config Actions
- Container Actions
- Edge Group Actions
- Edge Stack Actions
Overview
This node integrates with the Portainer API to manage Docker and Portainer resources. Specifically, for the User - Get operation, it retrieves detailed information about a specific user by their user ID. This is useful in scenarios where you need to fetch user details such as username, roles, or other metadata stored in Portainer.
Practical examples include:
- Automating user audits by fetching user details.
- Integrating user data into workflows for notifications or access control.
- Synchronizing user information between Portainer and other systems.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose details you want to retrieve. |
Output
The node outputs JSON data representing the user object retrieved from the Portainer API. This typically includes fields such as user ID, username, role, and other user-specific metadata managed by Portainer.
No binary data output is involved in this operation.
Example output structure (simplified):
{
"Id": "1",
"Username": "admin",
"Role": "Administrator",
"Enabled": true,
"Created": "2023-01-01T12:00:00Z",
// ... other user details
}
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the Portainer API.
- The node expects the base URL of the Portainer instance to be set in the credentials.
- Network connectivity to the Portainer API endpoint is necessary.
Troubleshooting
- Invalid User ID: If the provided User ID does not exist, the API will return a 404 error. Verify that the User ID is correct.
- Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Ensure the API key is valid and has sufficient permissions.
- Network Issues: Connection timeouts or unreachable host errors indicate network problems or incorrect base URL configuration.
- API Rate Limits: Excessive requests may trigger rate limiting; implement retries or backoff if needed.
Links and References
This summary focuses on the User - Get operation of the Portainer node based on the provided source code and input properties.