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 Application → Update
AI-generatedSummary
Updates a CDC application configuration in Infoblox using its resource ID. Provide mapped fields and, optionally, a JSON body; JSON body values override mapped values with the same keys.
Inputs
- Resource ID (required) — Infoblox ID of the CDC application to update.
- Fields (required) — Map the application fields to update. Fields are loaded from the API schema when available; automatic mapping is supported.
- JSON Body — Additional request body as JSON, merged over mapped fields. Use for fields not in the schema; matching JSON keys take precedence.
- Query Parameters — Additional query parameter name/value pairs to send with the request.
Output shape
A single record or a list of records
The node sends a PUT request to the CDC applications endpoint for the specified ID and returns the API response. Array responses are emitted as separate n8n items; a non-array response is emitted as one item.