Actions109
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Websites Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Users Actions
- Activity Logs Actions
- Articles Actions
Overview
The "Create Network" operation for the "Networks" resource in this custom n8n node allows users to create a new network entity by sending relevant details to an external API (presumably Hudu, as indicated by the node's name). This is useful in scenarios where you need to automate the provisioning or documentation of network segments within your organization's infrastructure management workflows. For example, you might use this node to automatically register new VLANs, subnets, or other network resources when onboarding new locations or clients.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | The unique identifier for the network. |
| Name | String | The name of the network. |
| Address | String | The network address, typically in CIDR notation. |
| Network Type | Number | The type of network, represented as an integer. |
| Slug | String | A slug representing the network. |
| Company Id | Number | The identifier of the company that owns this network. |
| Location Id | Number | The identifier of the location associated with this network. |
| Description | String | A brief description of the network. |
| Created At | String | The date and time when the network was created. |
| Updated At | String | The date and time when the network was last updated. |
All these properties are optional and can be provided via the "Additional Body Fields" collection.
Output
The node outputs a json object containing the response from the API after attempting to create the network. The exact structure depends on the external API's response, but it will typically include details about the newly created network, such as its ID, name, address, and any other metadata returned by the service.
If the API supports binary data responses, the node may also output binary data, but for this operation, the primary output is expected to be JSON.
Dependencies
- External Service: Requires access to the Hudu API (or another compatible API as configured).
- API Key/Credentials: Needs valid credentials (
avantguardHuduApi) with abaseUrlproperty. - n8n Configuration: The base URL for the API must be set in the credentials used by the node.
Troubleshooting
Common Issues:
- Missing or Invalid Credentials: If the required API credentials are not provided or incorrect, the node will fail to connect to the API.
- Invalid Input Data: Supplying invalid values (e.g., malformed CIDR addresses, missing required fields as per backend validation) may result in API errors.
- Network/Connectivity Errors: If n8n cannot reach the specified API endpoint, the node will throw connection errors.
Common Error Messages:
"401 Unauthorized": Check your API key and permissions."400 Bad Request": Review the input fields for correctness and completeness."404 Not Found": Ensure the base URL and endpoint paths are correct."500 Internal Server Error": The issue may be on the API provider's side; try again later or contact support.