AvantGuard - WebhookSite icon

AvantGuard - WebhookSite

AvantGuard - WebhookSite

Actions100

Overview

The "Update Network" operation in the Networks resource allows users to modify details of an existing network by specifying its unique identifier and any fields they want to update. This node is useful for maintaining accurate and up-to-date network information within a system, such as updating network names, addresses, descriptions, or associated metadata.

Practical examples include:

  • Changing the name or description of a network after rebranding or restructuring.
  • Updating the network address if the subnet changes.
  • Modifying associated company or location identifiers when networks are reassigned.

Properties

Name Meaning
Id The unique numeric identifier of the network to update (required).
Additional Body Fields Optional additional fields to update on the network. Can include:
- Id Unique identifier for the network (number).
- Name The name of the network (string).
- Address The network address, typically in CIDR notation (string).
- Network Type The type of network represented as an integer (number).
- Slug A slug representing the network (string).
- Company Id Identifier of the company that owns this network (number).
- Location Id Identifier of the location associated with this network (number).
- Description A brief description of the network (string).
- Created At The date and time when the network was created (string).
- Updated At The date and time when the network was last updated (string).

Output

The node outputs JSON data representing the updated network object returned from the API after the update operation. This JSON will contain the current state of the network including all fields that were updated or retrieved.

If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON-based.

Dependencies

  • Requires an API key or authentication token configured in n8n credentials to authorize requests to the backend service managing networks.
  • The base URL for the API must be set in the node's credential configuration.
  • Uses HTTP headers Accept: application/json and Content-Type: application/json for communication.

Troubleshooting

  • Missing or invalid network ID: The operation requires a valid network ID; ensure the "Id" property is correctly set and corresponds to an existing network.
  • Invalid field values: Some fields like network address or dates must follow specific formats (e.g., CIDR notation for address, ISO string for dates). Invalid formats may cause API errors.
  • Authentication errors: Ensure the API key or authentication token is correctly configured and has permissions to update networks.
  • Network not found: If the specified network ID does not exist, the API will likely return a not found error.
  • API connectivity issues: Verify the base URL and network connectivity to the API endpoint.

Links and References

Discussion