Actions88
- Module Actions
- Platform Actions
- Device Actions
- Device Bay Actions
- Device Bay Template Actions
- Device Role Actions
- Device Type Actions
- Interface Actions
- Manufacturer Actions
- Module Bay Actions
- Module Bay Template Actions
- Module Type Actions
- Region Actions
- Site Actions
- Virtual Chassis Actions
- Virtual Device Context Actions
Overview
This node integrates with the NetBox API, a popular infrastructure resource modeling tool used for managing IP addresses, devices, racks, and other network-related resources. Specifically, the "Site" resource with the "Get" operation allows users to retrieve detailed information about a particular site within the NetBox system by specifying its unique Site ID.
Common scenarios where this node is beneficial include:
- Automating retrieval of site details for network documentation or auditing.
- Integrating site data into workflows that require location-specific configurations.
- Synchronizing site information between NetBox and other systems.
For example, a user might use this node to fetch the details of a data center site by providing its Site ID, then use that data downstream in an automation workflow to provision equipment or update inventory records.
Properties
| Name | Meaning |
|---|---|
| Domain | The domain of the NetBox API to target. Options: DCIM, IPAM, Tenancy, Extras, Virtualization, Circuits, Core, Users, Plugins, VPN, Wireless, Status. For this operation, "dcim" is relevant. |
| Site ID | The unique identifier of the site to retrieve. This is a required string input specific to the "Site" resource under the "dcim" domain. |
Output
The node outputs JSON data representing the retrieved site record from NetBox. This JSON includes all the fields and metadata associated with the site as returned by the NetBox API, such as site name, slug, description, physical address, contact info, and any custom fields configured in NetBox.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a NetBox instance via its REST API.
- Needs an API authentication token or key credential configured in n8n to authorize requests to the NetBox API.
- The node depends on internal helper functions (from
./helpers/executeOperation) to perform the actual API call based on the selected domain, resource, and operation.
Troubleshooting
Common issues:
- Invalid or missing Site ID will cause the API request to fail.
- Incorrect domain or resource selection may result in no data or errors.
- Network connectivity problems or incorrect API credentials will prevent successful execution.
Error messages:
- Errors thrown during execution are logged and, if "Continue on Fail" is enabled, returned as part of the node's output JSON under an
errorfield. - Typical error messages include authentication failures, resource not found (e.g., invalid Site ID), or API rate limiting.
- Errors thrown during execution are logged and, if "Continue on Fail" is enabled, returned as part of the node's output JSON under an
Resolutions:
- Verify the Site ID exists in NetBox and is correctly entered.
- Ensure the API key or token has sufficient permissions.
- Check network access to the NetBox server.
- Enable "Continue on Fail" to handle errors gracefully in workflows.