Overview
This node integrates with the WiGLE (Wireless Geographic Logging Engine) API to search for WiFi networks based on various filters such as SSID, BSSID, geolocation coordinates, and address components. It is useful for scenarios where you want to discover or analyze wireless networks in a specific area or matching certain criteria. For example, it can be used by network administrators to audit nearby WiFi networks, by security professionals to identify potentially unauthorized access points, or by developers building location-aware applications that leverage WiFi data.
Properties
| Name | Meaning |
|---|---|
| Search by SSID | Filter networks by SSID name pattern. Supports wildcard characters % and _. |
| Search by BSSID | Filter networks by BSSID (MAC address format, e.g., 0A:2C:EF). |
| Filter By Geo | Enable filtering by geographic coordinates (latitude, longitude, radius). |
| Latitude | Latitude coordinate for geo-filtering (shown if "Filter By Geo" is enabled). |
| Longitude | Longitude coordinate for geo-filtering (shown if "Filter By Geo" is enabled). |
| Radius (Km) | Radius in kilometers around the specified latitude/longitude to filter networks (geo-filter). |
| Filter By Location | Enable filtering by address components like road, city, region, postal code, and country. |
| Road | Street or road name for location-based filtering (shown if "Filter By Location" is enabled). |
| City | City name for location-based filtering (shown if "Filter By Location" is enabled). |
| Region | Region or state name for location-based filtering (shown if "Filter By Location" is enabled). |
| Postal Code | Postal or ZIP code for location-based filtering (shown if "Filter By Location" is enabled). |
| Country | Country name for location-based filtering (shown if "Filter By Location" is enabled). |
| Results per Page | Number of results to return per page (default 25). |
| Put Results in Field | The name of the output field where the search results will be stored (default "wigle"). |
Output
The node outputs JSON data containing the search results from the WiGLE API under a user-defined field (default is "wigle"). This field contains an object with the property results, which is an array of WiFi network entries matching the search criteria. Each entry typically includes details such as SSID, BSSID, location coordinates, and other metadata provided by WiGLE.
No binary data output is produced by this node.
Example output structure:
{
"wigle": {
"results": [
{
"ssid": "ExampleNetwork",
"netid": "00:11:22:33:44:55",
"trilat": 37.7749,
"trilong": -122.4194,
...
},
...
]
}
}
Dependencies
- Requires an active WiGLE API key credential configured in n8n.
- Makes HTTP GET requests to the WiGLE API endpoint
https://api.wigle.net/api/v2/network/search. - The node expects the API key to be provided via basic authorization header.
Troubleshooting
- Request error (400): Usually indicates invalid query parameters. Verify that filters like SSID, BSSID, or location fields are correctly formatted.
- Insufficient balance (402): The WiGLE account associated with the API key does not have enough quota or credits for commercial queries. Check your WiGLE account status.
- Query Failed (410): The query was rejected by the server. This might happen if the request is malformed or violates API usage policies.
- Too many queries (429): Rate limit exceeded. Reduce the frequency of requests or upgrade your WiGLE plan.
- Unknown errors: Could be due to network issues or unexpected API responses. Check connectivity and API key validity.
Links and References
- WiGLE API Documentation
- WiGLE Website
- n8n HTTP Request Node Documentation (for understanding HTTP calls)