InfobloxInstall

Summary

Updates an existing Infoblox identity group by ID, sending a PATCH request to the Identity service's /v2/groups/{id} endpoint with a body built from mapped fields and optional JSON.

Inputs

• resourceId (required) — ID of the identity group to update. It is URL-encoded and appended to /v2/groups/.
• dataFields (required) — Resource mapper for the fields to change. Columns load from the Infoblox 'Identity' API schema (read-only fields, id and _ref are skipped). Values you set here form the request body.
• jsonBody — Extra request body as JSON, merged over the mapped fields. Keys here override mapped keys. Use it for fields missing from the schema. Defaults to {}.
• queryParameters — Optional name/value pairs added to the request query string.

Output shape

One output item per input item, containing the JSON response from the API for the updated group. If the response is not an object, it is wrapped as { result: value }.

The update uses PATCH, because identityGroup is not in the PUT or POST update lists, so only the supplied fields should change. This relies on the API's PATCH semantics, which the source does not confirm. If the API call fails, the node throws an error, or with Continue On Fail it outputs { error: message } for that item. The operation uses the Infoblox CSP API credentials.

Examples

Example 1: Rename an identity group and change its description.

Resource: Identity: Group; Operation: Update; Resource ID: the group ID; Fields: map name and description to the new values.

Example 2: Set a field that the schema doesn't list.

Resource ID: group ID; JSON Body: {"description":"Updated by n8n"}.

Links

• n8n community nodes installation guide