AvantGuard - WebhookSite icon

AvantGuard - WebhookSite

AvantGuard - WebhookSite

Actions100

Overview

This node operation allows users to create a new network resource by sending specified network details to an external service. It is useful in scenarios where automated network management or provisioning is required, such as setting up new network segments for different company locations or projects. For example, a user can automate the creation of networks with specific addresses and descriptions directly from their workflow without manual intervention.

Properties

Name Meaning
Additional Body Fields Optional fields to specify additional details about the network. These include:
- Id The 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.
- Slug A slug representing the network (string).
- Company Id The identifier of the company that owns this network (number).
- Location Id The 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).

These fields are optional and can be added as needed to provide more context or metadata about the network being created.

Output

The output of this node will contain a JSON object representing the newly created network resource as returned by the external API. This JSON typically includes all the properties sent in the request along with any additional data assigned by the server, such as unique identifiers or timestamps.

If the node supports binary data output, it would represent any binary content related to the network creation response, but based on the provided information, the output is primarily JSON.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to authorize requests to the external service.
  • The base URL for the API must be set in the node credentials configuration.
  • Depends on the external API endpoint that handles network creation.

Troubleshooting

  • Common Issues:

    • Missing or invalid API credentials can cause authentication failures.
    • Providing invalid or incomplete network data (e.g., malformed address) may result in validation errors from the API.
    • Network connectivity issues can prevent successful API calls.
  • Error Messages:

    • Authentication errors typically indicate missing or incorrect API keys; verify credentials in n8n.
    • Validation errors from the API will specify which fields are incorrect or missing; review and correct input properties accordingly.
    • Timeout or connection errors suggest network problems; check internet connectivity and API availability.

Links and References

  • Refer to the external API documentation for detailed information on network resource creation and field requirements.
  • n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.

Discussion