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 Category Filter → Create
AI-generatedSummary
Create a Threat Defense category filter in Infoblox using mapped fields and optional JSON body data. The node sends a POST request to the category filters endpoint and returns the API response.
Inputs
- Fields (required) — Map the category filter fields. Available fields are loaded from the Infoblox API schema when available; auto-map is supported.
- JSON Body — Optional JSON properties merged over mapped fields, so these values override mapped values with the same keys. Use for fields missing from the schema.
- Query Parameters — Optional name/value query parameters to include with the request.
Output shape
A single record containing the API response, or multiple records if the response is an array.
The response is passed through as JSON. If the request fails and Continue On Fail is enabled, the output contains an error field.