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 the Nginx Proxy Manager (NPM) API, allowing users to manage various NPM resources programmatically. Specifically, for the User - Update operation, it updates user details such as email, name, nickname, and status flags like disabled or admin. This is useful in scenarios where automated user management is needed, for example, syncing user data from an external system, enabling/disabling users based on business rules, or updating user roles without manual intervention.
Practical examples:
- Automatically disable a user account after a certain period of inactivity.
- Update user contact information when it changes in a central directory.
- Promote a user to admin role based on workflow conditions.
Properties
| Name | Meaning |
|---|---|
| ID | The unique numeric identifier of the user to update. |
| Options | A collection of optional fields to update for the user: |
| - Email: The user's email address. | |
| - Name: The full name of the user. | |
| - Nickname: A nickname or alias for the user. | |
| - Disabled: Boolean flag to enable or disable the user account. | |
| - Admin: Boolean flag to grant or revoke administrative privileges for the user. |
Output
The node outputs a JSON array containing the response from the Nginx Proxy Manager API after attempting to update the user. The structure typically includes confirmation of the updated user data or error details if the update failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential with access to the Nginx Proxy Manager instance.
- The node authenticates by sending the stored email and password to obtain a token before making API requests.
- The base URL of the NPM instance must be configured in the credentials.
- Network connectivity to the NPM API endpoint is necessary.
Troubleshooting
- Login failed: No token received: Indicates authentication failure. Verify that the provided email and password in the credentials are correct and that the NPM instance is reachable.
- Invalid user ID: Ensure the user ID specified exists in the NPM system.
- Permission errors: The API user may lack rights to update users; check API user permissions.
- Network errors/timeouts: Confirm network connectivity and that the NPM API endpoint URL is correct.
- Empty or missing required fields: The ID field is mandatory; ensure it is provided and valid.
Links and References
- Nginx Proxy Manager GitHub Repository
- Nginx Proxy Manager API Documentation (if available)
- n8n Documentation on Creating Custom Nodes