NetBox icon

NetBox

Consume NetBox API

Actions243

Power Port Template → Create

AI-generated

Overview

This node interacts with the NetBox API to create a new Power Port Template within the DCIM domain. It is useful for network administrators and data center managers who want to automate the creation of power port templates associated with specific device types in their infrastructure management system. For example, it can be used to define standardized power port templates for different device types to ensure consistent configuration across devices.

Use Case Examples

  1. Creating a power port template for a new device type to standardize power port configurations.
  2. Automating the addition of power port templates during device type onboarding in NetBox.

Properties

Name Meaning
Domain Specifies the domain of the NetBox API to interact with, here it is set to 'dcim' for data center infrastructure management.
Device Type ID The ID of the device type to which this power port template belongs.
Name The name of the power port template to be created.
Additional Fields Optional additional fields for the power port template such as module type ID, label, type of power port, maximum and allocated power draw, and description.

Output

JSON

  • id - Unique identifier of the created power port template.
  • device_type_id - ID of the device type associated with the power port template.
  • name - Name of the created power port template.
  • module_type - Module type ID if specified.
  • label - Label of the power port template.
  • type - Type of power port connector.
  • maximum_draw - Maximum power draw in watts.
  • allocated_draw - Allocated power draw in watts.
  • description - Description of the power port template.

Dependencies

  • NetBox API with appropriate credentials

Troubleshooting

  • Ensure the Device Type ID is valid and exists in NetBox to avoid errors.
  • Verify that the API credentials have permissions to create power port templates in the DCIM domain.
  • If the node throws an error, check the error message for details; enabling 'Continue on Fail' allows the workflow to proceed with error output.

Discussion