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, and other network resources. Specifically, the "Device" resource with the "Get Config Context" operation allows users to retrieve configuration context data related to devices within NetBox.
Typical use cases include:
- Automating retrieval of device configuration contexts for network automation workflows.
- Integrating device metadata into broader IT or network management processes.
- Using configuration context data to drive conditional logic or enrich other systems.
For example, a user might use this node to fetch the configuration context of a specific device to dynamically generate configuration files or to audit device settings.
Properties
| Name | Meaning |
|---|---|
| Domain | The domain of the NetBox API to target. Options include: DCIM, IPAM, Tenancy, Extras, Virtualization, Circuits, Core, Users, Plugins, VPN, Wireless, Status. For this operation, "dcim" is typically selected. |
Note: The provided input properties JSON only includes the "Domain" property because the user requested details for the Device resource and Get Config Context operation. The node's full property list includes many resources and operations filtered by domain.
Output
The node outputs JSON data representing the response from the NetBox API for the requested resource and operation. In this case, it will return the configuration context information related to devices.
The output structure generally contains:
- A
jsonfield with the API response data, which includes details of the device's config context. - If an error occurs and "Continue on Fail" is enabled, the output will contain a JSON object with an
errorfield describing the issue.
The node does not explicitly handle binary data output.
Dependencies
- Requires access to a NetBox instance with its API enabled.
- Needs an API authentication token or key configured in n8n credentials (referred generically as "an API key credential").
- The node depends on an internal helper function (
executeOperation) to perform the actual API call.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- Incorrect domain or resource selection leading to API errors.
- Network connectivity problems preventing access to the NetBox API endpoint.
Error messages:
- Errors thrown during execution are logged to the console.
- If "Continue on Fail" is enabled, errors are returned as part of the node output under an
errorfield. - To resolve errors, verify API credentials, ensure correct domain/resource selections, and check network connectivity.