AvantGuard - WebhookSite icon

AvantGuard - WebhookSite

AvantGuard - WebhookSite

Actions100

Overview

This node operation allows users to create (post) a new rack storage entity in an external system. Rack storages typically represent physical or logical storage units within data centers or warehouses, where equipment like servers or networking devices can be mounted.

Common scenarios for this node include:

  • Automating the addition of new rack storage locations when expanding infrastructure.
  • Integrating inventory management systems with physical asset tracking.
  • Synchronizing rack storage data between different platforms.

For example, a user could automate creating rack storage entries whenever a new location is added in their facility management software, ensuring consistent and up-to-date records across systems.

Properties

Name Meaning
Additional Body Fields Optional fields to specify details about the rack storage. These include:
- Id The unique ID of the rack storage (number).
- Location Id The unique ID of the location where the rack storage is situated (number).
- Name The name assigned to the rack storage (string).
- Description A textual description of the rack storage (string).
- Max Wattage The maximum wattage capacity the rack storage can handle (number).
- Starting Unit The starting unit number of the rack storage (number).
- Height The height dimension of the rack storage (number).
- Width The width dimension of the rack storage (number).
- Created At Timestamp indicating when the rack storage was created (string, date-time format).
- Updated At Timestamp indicating the last update time of the rack storage (string, date-time format).
- Discarded At Timestamp indicating when the rack storage was discarded; can be null if not discarded (string).
- Company Id The unique ID of the company owning or responsible for the rack storage (number).

All these fields are optional and can be provided as part of the request body to customize the rack storage creation.

Output

The node outputs JSON data representing the newly created rack storage object as returned by the external API. This JSON will include all relevant properties of the rack storage, such as its ID, name, dimensions, timestamps, and any other metadata provided or generated by the system.

There is no indication that the node outputs binary data.

Dependencies

  • Requires an API key or authentication token credential configured in n8n to authorize requests to the external service managing rack storages.
  • The base URL for the API must be set in the node credentials.
  • The node depends on an OpenAPI-based client library internally but this is abstracted away from the user.

Troubleshooting

  • Missing or invalid authentication: Ensure the API key or authentication token is correctly configured and has sufficient permissions to create rack storages.
  • Invalid field values: Providing incorrect data types (e.g., string instead of number) or invalid IDs may cause API errors. Validate input fields before execution.
  • Network issues: Connectivity problems to the API endpoint will result in request failures.
  • API limits or restrictions: The external service might enforce rate limits or require certain mandatory fields; check API documentation if errors occur.

Common error messages might include unauthorized access, validation errors for missing or malformed fields, or server errors. Reviewing the exact API response message will help diagnose the issue.

Links and References

  • Refer to the external API documentation for rack storage entities for detailed field descriptions and constraints.
  • n8n documentation on how to configure API credentials and use HTTP request nodes may be helpful for setup.

Discussion