Actions6
- Community Actions
- Enterprise Actions
Overview
This node integrates with the GreyNoise API to provide information about IP addresses and network noise data. Specifically, for the Community IP operation under the Community resource, it performs a free community IP lookup. This allows users to query details about a single IP address as observed by GreyNoise's community dataset.
Common scenarios where this node is beneficial include:
- Quickly checking if an IP address is known for scanning or attacking activity on the internet.
- Gathering contextual threat intelligence about an IP from publicly available GreyNoise community data.
- Automating IP reputation lookups in security workflows without requiring enterprise-level access.
For example, a security analyst could input an IP address suspected of malicious activity and receive information about its behavior or classification from the GreyNoise community dataset.
Properties
| Name | Meaning |
|---|---|
| IP | The IP address to query against the GreyNoise Community API. This is a required string input. |
Output
The node outputs JSON data representing the response from the GreyNoise Community IP endpoint. This typically includes information such as:
- Whether the IP is classified as benign or malicious.
- Metadata about the IP’s activity observed by GreyNoise sensors.
- Any tags or labels associated with the IP.
- Additional context like last seen timestamps or network owner info (depending on API response).
No binary data output is produced by this operation.
Dependencies
- Requires access to the GreyNoise API endpoint at
https://api.greynoise.io/v3/community/{ip}. - Optionally uses an API key credential for authenticated requests, though the community IP lookup may work without authentication.
- No additional environment variables are explicitly required beyond standard n8n credential setup for API keys if used.
Troubleshooting
- Invalid IP format error: Ensure the IP property is a valid IPv4 or IPv6 address string.
- API rate limits or access denied: If using an API key, verify that it is valid and has sufficient permissions. The community endpoint may have stricter rate limits.
- Empty or unexpected response: Confirm the IP exists in the GreyNoise community dataset; some IPs may not have data.
- Network connectivity issues: Verify that n8n can reach
api.greynoise.ioand that no firewall blocks outbound HTTPS requests.