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 Application Filter → Create
AI-generatedSummary
Create a Threat Defense application filter in Infoblox Cloud by sending a POST request with mapped fields and any additional JSON body fields.
Inputs
- Fields (required) — Map the filter fields available from the Infoblox API schema. The node uses the mapped values as the request body.
- JSON Body — Additional request body fields as JSON. These are merged over the mapped fields, so JSON values take precedence when keys overlap.
- Query Parameters — Optional name/value pairs added to the request query string.
Output shape
A single record, or multiple items if the API response is an array.
The node sends a POST request to the Infoblox application filters endpoint and converts each returned value into an n8n output item. If execution is configured to continue on failure, an error is returned in an item’s
errorfield.