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, the "User" resource with the "Create" operation enables creating new user accounts in the NPM system. This is useful for automating user management tasks such as onboarding new administrators or standard users without manual intervention through the NPM UI.
Practical examples include:
- Automatically creating a new user when a new employee joins your organization.
- Setting up multiple users with different roles and access levels via workflow automation.
- Integrating user creation into broader infrastructure provisioning pipelines.
Properties
| Name | Meaning |
|---|---|
| The email address of the new user. | |
| Name | The full name of the new user. |
| Nickname | A nickname or username for the new user. |
| Disabled | Whether the user account should be disabled upon creation (true or false). |
| Admin | Whether the user should have administrative privileges (true or false). |
Output
The node outputs a JSON array containing the response from the Nginx Proxy Manager API after attempting to create the user. This typically includes details about the newly created user such as their ID, email, name, nickname, status flags (disabled/admin), and possibly timestamps or metadata returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to an Nginx Proxy Manager instance.
- Needs credentials including the URL, email, and password for authentication to obtain an API token.
- The node uses the NPM API token to authorize requests.
- Proper configuration of the API credentials in n8n is necessary before use.
Troubleshooting
- Login failed: No token received: This error indicates that authentication with the NPM API failed. Verify that the provided credentials (email, password, and URL) are correct and that the NPM instance is reachable.
- HTTP request errors: Network issues, incorrect URLs, or API endpoint changes can cause failures. Ensure the base URL is correct and the NPM server is accessible.
- Validation errors: Missing required fields like email, name, or nickname will cause the API to reject the request. Make sure all required properties are provided.
- Permission errors: If the authenticated user does not have rights to create users, the API will deny the request. Confirm the credentials used have sufficient permissions.
Links and References
- Nginx Proxy Manager Official Documentation
- Nginx Proxy Manager API Reference (if available) (Note: Replace with actual link if known)