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 → Get Many
AI-generatedSummary
Retrieve TD application filters from the Infoblox Cloud API. Optionally apply a server-side filter expression or extra query parameters, and choose whether to return up to a limit or fetch all available results.
Inputs
- Return All — Defaults to false. When false, requests up to the Limit (default 50); when true, fetches results in pages of 100 until no more remain.
- Limit — Maximum results to request when Return All is false; defaults to 50.
- Filter Expression — Optional Infoblox
_filterexpression applied server-side, such asname=="default". Leave empty for no expression filter. - Query Parameters — Optional additional query parameters, supplied as name/value pairs and passed to the API. For example, Universal DDI filters can use
_filteror_fields; these parameters are combined with the filter expression, with additional query parameters taking precedence if they use the same name.
Output shape
A list of matching filter records, emitted as n8n output items.
The API response is treated as a list when it is an array or contains an array under
results,result,items, ordata; otherwise the response is passed through as one output item. Each output item is paired with its corresponding input item.