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 within n8n workflows. Specifically, the "Access List" resource with the "Get Many" operation retrieves multiple access lists from the NPM server. This is useful for scenarios where you want to automate monitoring or reporting on access control configurations, synchronize access lists with other systems, or dynamically adjust workflows based on access list data.
For example, a user might use this node to fetch all access lists and then filter or process them to update firewall rules elsewhere or generate audit reports.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional parameters to customize the request: |
| - Expand Owner | Boolean flag to include detailed information about the owner of each access list. |
| - Expand Clients | Boolean flag to include detailed information about clients associated with each access list. |
| - Expand Items | Boolean flag to include detailed information about items within each access list. |
| - Filter | A string to filter the results by the name of the access list. |
Output
The node outputs a JSON array containing the retrieved access lists. Each item in the array represents an access list object, potentially expanded with owner, clients, and items details depending on the selected options.
If binary data were involved (not applicable here), it would be summarized accordingly, but this node deals purely with JSON data representing access list entities.
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 performs an authentication step to obtain a token before making further API requests.
- No additional external services are required beyond the NPM API.
Troubleshooting
- Login failed: No token received: This error indicates that authentication with the NPM API failed. Verify that the provided URL, email, and password credentials are correct and that the NPM instance is reachable.
- Network issues or timeouts: Ensure the NPM server is accessible from the environment where n8n runs.
- Empty or unexpected results: Check if the filter string is too restrictive or if the expand options are set correctly.
- Permission errors: Confirm that the authenticated user has sufficient permissions to read access lists.
Links and References
- Nginx Proxy Manager Official Documentation
- Nginx Proxy Manager API Reference (if available)
- n8n Documentation for general node usage and credential setup guidance