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
Location → Create
AI-generatedSummary
Creates a new location in Infoblox Universal DDI (Infrastructure API) by sending a POST to /api/infra/v1/locations with a body built from mapped fields and optional JSON.
Inputs
- dataFields (required) — Resource mapper listing writable fields loaded from the Infoblox 'Locations' API schema (required fields first; id and read-only fields are skipped). Supports auto-mapping from input data. If the schema can't be loaded, use JSON Body instead.
- jsonBody — JSON object merged over the mapped fields (JSON values win on key conflicts). Use for fields not in the schema. Defaults to {}.
- queryParameters — Extra name/value query-string parameters appended to the POST request.
Output shape
One output item per input item, containing the API's response for the created location (typically the new location record).
Non-object responses are wrapped as {result: value}. With Continue On Fail, errors are returned as {error: message} for that item. Requires Infoblox CSP API credentials.
Examples
Example 1: Register a new datacenter location for on-prem hosts
Resource: Location, Operation: Create; map name (and other schema fields such as address details) in Fields.
Example 2: Create a location using a field not in the schema
Leave Fields minimal (e.g. name) and set JSON Body to {"name":"HQ","description":"Main office"}.