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
Redirect: Custom Redirect → Update
AI-generatedSummary
Update a custom redirect in Infoblox by resource ID, sending mapped fields and any additional JSON body as a PUT request. The operation can also include extra query parameters and returns the API response.
Inputs
- Resource ID (required) — Infoblox ID of the custom redirect to update.
- Fields (required) — Map the redirect fields to update. Available mapping fields are loaded from the API schema when available; automatic mapping is supported.
- JSON Body — Optional JSON properties merged over the mapped fields, so these values take precedence when keys overlap. Use it for fields missing from the schema.
- Query Parameters — Optional name/value pairs appended to the request query string.
Output shape
A single record containing the API response, or one record per item if the response is an array.
The request uses PUT at the custom redirect endpoint for the specified resource ID. If Continue On Fail is enabled, errors are returned as an item with an error field.