Actions182
- Address Block Actions
- Audit Log Actions
- Auth Profile: LDAP Actions
- Auth Profile: OIDC Actions
- Auth Profile: SAML Actions
- CDC Application Actions
- CDC Destination: HTTP Actions
- CDC Destination: Splunk Actions
- CDC Destination: Syslog Actions
- CDC Host Actions
- Custom API Request Actions
- DFP Service Actions
- DHCP Fingerprint Actions
- DHCP Lease Actions
- DNS Event Actions
- DNS Record Actions
- DNS Zone Actions
- Endpoint Device Group Actions
- Endpoint Roaming Device Actions
- Endpoint VPN Profile Actions
- Fixed Address Actions
- Global Search Actions
- Identity: Compartment Actions
- Identity: Group Actions
- Identity: User Actions
- Infrastructure Host Actions
- Infrastructure Service Actions
- IP Address Actions
- IP Space Actions
- IPAM Range Actions
- Location Actions
- Lookalike Domain Actions
- Lookalike Target Actions
- NIOS Custom API Request Actions
- NIOS WAPI Object Actions
- NTP Service Config Actions
- Redirect: Custom Redirect Actions
- Service Log Actions
- SOC Insight Actions
- Subnet Actions
- TD Access Code Actions
- TD Application Filter Actions
- TD Category Filter Actions
- TD Internal Domain List Actions
- TD Named List Actions
- TD Scheduled Report Actions
- TIDE Batch Actions
- TIDE Dossier Lookup Actions
- TIDE Threat Actions
IP Address → Update
AI-generatedSummary
Updates an existing Infoblox Universal DDI IP address (IPAM address) by resource ID, sending a PATCH request to /api/ddi/v1/ipam/address/{id} with the fields you map or supply as JSON.
Inputs
- resourceId (required) — The Infoblox ID of the IP address record to update. It is URL-encoded and appended to the endpoint path.
- dataFields (required) — Resource mapper for the request body. Columns are loaded from the Infoblox IPAM API schema (Ipamsvc), skipping read-only fields, id and _ref. If the schema can't be loaded, use JSON Body instead.
- jsonBody — Additional request body as JSON, merged over the mapped fields. JSON keys win on conflict. Use it for fields missing from the schema. Defaults to {}.
- queryParameters — Name/value pairs added to the request query string, for example _fields.
Output shape
A single JSON item per input item containing the API response, normally the updated IP address object.
Non-object responses are wrapped as { result: value }. With Continue On Fail enabled, a failed item returns { error: message } instead of stopping the workflow. Requires Infoblox CSP API credentials.
Examples
Example 1: Change the comment on a known IP address record.
Resource: IP Address; Operation: Update; Resource ID: the address ID; JSON Body: {"comment":"Reserved for printer"}.
Example 2: Update the address's fields using values from an earlier node.
Resource ID: {{$json.id}}; add the needed fields in Fields (mapped from the schema) with expressions for their values.