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
TD Named List → Create
AI-generatedSummary
Create a Threat Defense named list by sending a POST request to the Infoblox named lists endpoint. Map fields from the available API schema or provide additional JSON fields; JSON Body values override mapped values with the same names.
Inputs
- Fields (required) — Map the named list fields. The available fields depend on the Infoblox API schema; automatic mapping is supported.
- JSON Body — Additional request body as JSON. Merged over mapped fields, so matching JSON properties take precedence. Use it for fields missing from the schema or when no schema is available.
- Query Parameters — Optional name/value query parameters added to the request.
Output shape
A single record or a list of items, depending on the API response.
The node converts an array response into one output item per element; otherwise it returns the response as one item. Each output item is paired with its input item.