Actions100
- Activity Log Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Folder Actions
- IP Address Actions
- List Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
Overview
This node interacts with the Hudu REST API to perform various operations on different resources. Specifically, for the Network resource with the Get operation, it retrieves detailed information about a specific network identified by its ID. This is useful in scenarios where you need to fetch network details from your Hudu instance for documentation, auditing, or integration purposes.
Practical examples include:
- Automatically retrieving network configurations to update internal documentation.
- Integrating network data into other systems or dashboards.
- Triggering workflows based on network attributes fetched dynamically.
Properties
| Name | Meaning |
|---|---|
| Network ID | The unique numeric identifier of the network to retrieve. |
Output
The node outputs JSON data representing the network's details as returned by the Hudu API. Each output item corresponds to one network object containing all relevant fields such as network name, description, IP ranges, and other metadata defined by Hudu.
If the node supports binary data (not indicated here), it would typically represent attachments or files related to the network, but this operation primarily returns structured JSON data.
Dependencies
- Requires an active connection to the Hudu REST API.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL for the Hudu API must be set correctly in the node credentials.
Troubleshooting
Common issues:
- Invalid or missing Network ID will cause the API call to fail.
- Incorrect API key or base URL configuration leads to authentication errors.
- Network not found errors if the specified Network ID does not exist.
Error messages:
"The resource "networks" is not known!"— indicates an invalid resource parameter; ensure "networks" is selected.- API response errors such as 404 Not Found or 401 Unauthorized should be checked against the provided Network ID and API credentials.
Resolution tips:
- Verify that the Network ID is correct and exists in your Hudu instance.
- Confirm API credentials and base URL are properly configured.
- Use the node’s continue-on-fail option to handle errors gracefully in workflows.
Links and References
- Hudu API Documentation (for detailed API endpoints and data structures)
- n8n Documentation on Creating Custom Nodes