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 → Create
AI-generatedSummary
Creates a new Cloud Data Connector (CDC) application in Infoblox Portal by sending a POST to /api/cdc-flow/v1/applications with a body built from mapped fields and optional JSON.
Inputs
- Fields (dataFields) (required) — Resource mapper listing writable fields from the Infoblox CDC API schema (loaded live from the portal's apidoc spec). Required schema fields are listed first; read-only fields, id and _ref are skipped. If the schema can't be loaded, the list is empty and you should use JSON Body.
- JSON Body — JSON object merged over the mapped fields (JSON keys win on conflict). Use for fields missing from the schema. Defaults to {}; invalid JSON causes an error.
- Query Parameters — Extra name/value pairs added to the request query string.
Output shape
One output item per input item containing the JSON response from the API, normally the created CDC application record.
Non-object responses are wrapped as {result: value}. With Continue On Fail enabled, a failed item outputs {error: message}. Requires Infoblox CSP API credentials.
Examples
Example 1: Create a CDC application using schema fields
Resource: CDC Application, Operation: Create; map the required fields (e.g. name) in Fields; leave JSON Body as {}.
Example 2: Create an application with a field not in the schema
Leave Fields mostly empty and set JSON Body to a full JSON object of the application definition.