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: Splunk → Update
AI-generatedSummary
Update a CDC Splunk destination by Infoblox resource ID. Map fields or provide additional JSON properties; the node sends a PUT request to the destination endpoint and returns Infoblox’s response.
Inputs
- Resource ID (required) — Infoblox resource ID of the CDC Splunk destination to update.
- Fields (required) — Map destination fields using the API schema when available; supports automatic mapping.
- JSON Body — Additional JSON properties merged over mapped fields. Use for fields absent from the schema or when no schema is available.
- Query Parameters — Optional name/value query parameters to include in the request.
Output shape
The Infoblox API response, emitted as one or more n8n items.
Each response object becomes an item; array responses are split into items. Primitive response values are wrapped in a
resultproperty.