Actions82
- Device Actions
- Access Points Actions
- Get All Access Points
- Get Access Point Details
- Get Top APs by Wireless Usage
- Get AP Throughput Trends
- Get AP CPU Utilization
- Get AP Memory Utilization
- Get AP Power Consumption
- Get AP Radio Details
- Get Radio Performance
- Get APs with Performance Issues
- Get AP Port Frame Trends
- Get All Radios
- Get Radio Channel Utilization
- Get Radio Channel Quality
- Get Radio Noise Floor
- Get Radio Transmission Info
- Get AP Port CRC Errors
- Get AP Port Collision Errors
- Get AP Radio Throughput Trend
- Get AP Port Throughput Trend
- Get AP Radios List
- Get AP Ports List
- Get All WLANs
- Get WLAN by Name
- Get AP WLANs List
- Get AP WLAN Throughput Trend
- Get AP Tunnels List
- Get AP Tunnel Details
- Get AP Tunnel Throughput Trend
- Get AP Tunnel Packet Loss Trend
- Get AP Tunnel Jitter Trend
- Get AP Tunnel Latency Trend
- Get AP Tunnel MOS Score Trend
- Get WLAN Throughput Trend
- Client Actions
- Site Actions
- Site Health Actions
- Gateway Actions
- List Gateways
- Gateway Details
- Gateway Cluster Leader Details
- Gateway Cluster VLAN Mismatch Summary
- Gateway Cluster Connectivity Graph
- Gateway VLAN Detail
- List Gateway Cluster Members
- Gateway Tunnel Detail
- List Gateway Wired Interfaces
- List Gateway Cluster Tunnels
- List Gateway VLANs
- List Gateway LAN Tunnels
- List Gateway WAN Interfaces
- Get Gateway CPU Utilization Trend
- Get Gateway Memory Utilization Trend
- Get Gateway LAN Tunnel Throughput Trend
- Get Gateway LAN Tunnel Status Trend
- Get Cluster Capacity Trend
- Get Cluster Member Capacity Trend
- Get Gateway Interface Throughput Trend
- Get Summary of Cluster Tunnel Health
- Get Summary of Cluster Tunnel Status
- Get Summary of Gateway Tunnel Health
- Get Gateway WAN Availability Trend
- Get Gateway VPN Availability Trend
- Get Gateway Port Frames Trend
- Get Gateway Port Frames Errors Trend
- Get Gateway Port Frames Packets Trend
- Get Gateway Tunnel Dropped Packets Trend
- List Gateway WAN Tunnels
- Gateway WAN Tunnel Detail
- Get Summary of Gateway WAN Tunnel Health
- Get Details of Gateway Uplink
- Get Gateway Uplink Throughput Trend
- Get Gateway WAN Compression Trends for Uplink
- List Gateway Uplink Probes
- List Gateway Uplink Performance Trends
- Get Gateway Uplink Modem Stats
- Get WAN Availability Trends of Gateway Uplink
- Get VPN Availability Trends of Gateway Uplink
Overview
This node interacts with the Aruba Central Next Gen API to retrieve information about wireless LANs (WLANs) by their name within the Access Points resource. It is useful for network administrators who want to monitor or configure WLAN settings programmatically. For example, you can use this node to fetch details of a specific WLAN to verify its configuration or status without manually logging into the Aruba Central dashboard.
Properties
| Name | Meaning |
|---|---|
| Debug Mode | Whether to enable detailed debug logs for troubleshooting |
| Domain | API domain to interact with; options are: "Monitoring" (monitor devices, clients, and sites) or "Configuration" (configure devices, groups, and profiles) |
| WLAN Name | Name of the wireless LAN to retrieve |
Output
The node outputs JSON data representing the details of the requested WLAN identified by its name. The structure typically includes WLAN configuration and status information as returned by the Aruba Central Monitoring API. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Aruba Central Next Gen API.
- The node depends on the Aruba Central API domains "monitoring" or "configuration" depending on the selected domain property.
- No additional external dependencies beyond the Aruba Central API and n8n's OAuth2 credential setup are required.
Troubleshooting
- Common issues:
- Incorrect WLAN name may result in empty or error responses.
- Selecting the wrong domain ("monitoring" vs "configuration") could cause the operation to fail or return unexpected results.
- Missing or invalid API credentials will prevent successful API calls.
- Error messages:
- Errors during execution will be caught and logged with a message like "Node execution failed" followed by the specific error detail.
- If the node fails due to authentication, ensure the API key credential is correctly configured and has necessary permissions.
- Enable "Debug Mode" to get detailed logs which can help identify request/response issues.