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
CDC Destination: HTTP → Update
AI-generatedSummary
Updates an Infoblox CDC HTTP destination by ID, sending the selected field mappings together with any additional JSON body fields. The node uses a PUT request to the CDC destinations HTTP endpoint.
Inputs
- Resource ID (required) — Infoblox ID of the CDC HTTP destination to update.
- Fields (required) — Map destination fields using the available API schema. Auto-map is supported.
- JSON Body — Optional JSON object merged over the mapped fields; values here take precedence for duplicate keys. Use it for fields absent from the schema.
- Query Parameters — Optional additional request query parameters, such as Universal DDI filters _filter or _fields.
Output shape
A single record or a list of records, depending on the API response.
The response is passed through as JSON. Scalar response values are wrapped in an object under result. With Continue On Fail enabled, request errors are returned as an error field.