Hudu

Overview

This node interacts with the "Network" resource of an external system via its REST API, specifically supporting the Update operation for networks. It allows users to modify existing network records by specifying the network's unique identifier and updating one or more fields such as address, name, description, associated company, location, type, or slug.

Typical use cases include:

• Automating updates to network configurations in a centralized documentation or asset management system.
• Synchronizing network details from other systems or spreadsheets into the target platform.
• Bulk updating network metadata during migrations or audits.

For example, you could update the network address and description of a specific network identified by its ID, or change the company association of a network dynamically based on workflow logic.

Properties

Output

The node outputs JSON data representing the updated network object(s) returned from the API after the update operation. Each output item corresponds to an input item processed, enriched with the updated network details.

If the API supports binary data related to networks (not indicated here), it would be included accordingly, but this node primarily deals with JSON data.

Dependencies

• Requires an API key credential configured in n8n to authenticate requests against the external system's REST API.
• The base URL for the API must be set in the node credentials.
• The node relies on internal helper methods to perform HTTP requests and handle responses.
• Option loaders are used to populate selectable options for companies and possibly other fields.

Troubleshooting

• Common Issues:

  • Providing an invalid or non-existent Network ID will likely result in an error from the API indicating the network was not found.
  • Omitting required fields or providing invalid field formats (e.g., malformed CIDR in Address) may cause validation errors.
  • Insufficient permissions or incorrect API keys can lead to authentication failures.

• Error Messages:

  • "The resource \"networks\" is not known!" — This indicates the resource parameter was incorrectly set; ensure "networks" is selected.
  • API errors returned from the server will be passed through; check the message for details like "Not Found", "Unauthorized", or "Bad Request".

• Resolution Tips:

  • Verify that the Network ID exists and is correct.
  • Ensure all required credentials and API URLs are properly configured.
  • Validate field values before sending updates.
  • Use the node's "Continue On Fail" option to handle partial failures gracefully in batch operations.

Links and References

• n8n Expressions Documentation — For using expressions in property values.
• Refer to your external system's API documentation for detailed information about the network resource and update operation.