Actions38
- Access List Actions
- Certificate Actions
- Dead Host Actions
- Log Actions
- Proxy Host Actions
- Redirection Host Actions
- Setting Actions
- User Actions
Overview
This node integrates with an Nginx Proxy Manager (NPM) instance, allowing users to manage various NPM resources programmatically. Specifically, for the User - Get operation, it retrieves details of a user by their unique ID from the NPM system.
Common scenarios include:
- Automating user management workflows in NPM.
- Fetching user information for auditing or reporting purposes.
- Integrating NPM user data into broader IT infrastructure automation.
For example, you might use this node to fetch a user's details before updating permissions or to verify user existence during automated provisioning.
Properties
| Name | Meaning |
|---|---|
| ID | The unique numeric identifier of the user to retrieve from NPM. This is a required field. |
Output
The output is a JSON array containing the user object retrieved from the NPM API. This object typically includes user details such as username, email, roles, and other metadata defined by NPM's user schema.
No binary data is output by this node.
Example output structure (simplified):
[
{
"id": 123,
"username": "johndoe",
"email": "john.doe@example.com",
"role": "admin",
"isActive": true,
...
}
]
Dependencies
- Requires an active connection to an Nginx Proxy Manager instance.
- Needs credentials including URL, email, and password to authenticate via the NPM API.
- The node authenticates by requesting a token from the NPM API using these credentials before performing operations.
- Proper API access rights are necessary to retrieve user information.
Troubleshooting
- Login failed: No token received: Indicates authentication failure. Verify that the provided URL, email, and password credentials are correct and that the NPM instance is reachable.
- User not found or invalid ID: If the specified user ID does not exist, the API may return an error or empty response. Ensure the ID is valid and corresponds to an existing user.
- Network errors or timeouts: Check network connectivity to the NPM server and ensure the API endpoint is accessible.
- Insufficient permissions: The authenticated user must have rights to read user data; otherwise, the request will fail.
Links and References
- Nginx Proxy Manager GitHub Repository
- Nginx Proxy Manager API Documentation (if available)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls