InfobloxInstall

Summary

Updates an existing Infoblox Portal location (physical location for on-prem hosts) by ID, sending a PUT to /api/infra/v1/locations/{id} with the mapped fields and JSON body.

Inputs

• Resource ID (required) — ID of the location to update; URL-encoded and appended to the locations endpoint.
• Fields (required) — Resource mapper of fields loaded from the Infoblox 'Locations' API schema (read-only fields, id and _ref are skipped). Supports defining fields manually or auto-mapping from input data.
• JSON Body — Extra request body as JSON, merged over the mapped fields (JSON values win on conflict). Use for fields missing from the schema.
• Query Parameters — Optional name/value pairs added to the request query string.

Output shape

One output item per input item containing the API response for the updated location (typically the location record as JSON).

Uses PUT, so the body generally acts as a full replacement; include all fields you want to keep. Non-object responses are wrapped as { result: value }. With Continue On Fail, errors are returned as { error: message }. Requires Infoblox CSP API credentials.

Examples

Example 1: Rename a location and change its address

Resource: Location, Operation: Update, Resource ID: the location ID, Fields: name and address mapped (or JSON Body {"name":"HQ","address":{...}}).

Example 2: Update locations from upstream data

Resource ID set to {{$json.id}}, Fields in auto-map mode so incoming item properties are sent as the body.

Links

• n8n community nodes installation guide