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
TIDE Batch → Get Many
AI-generatedSummary
Retrieve TIDE batch records from Infoblox, optionally limiting the number returned and adding query parameters to filter or shape the response.
Inputs
- Return All — When false (default), return up to the Limit. When true, request up to 10,000 records; the TIDE batch request does not paginate beyond that.
- Limit — Maximum number of records to request when Return All is false; defaults to 50.
- Query Parameters — Optional name/value pairs sent as query parameters. The shared field description lists TIDE filters such as type, host, ip, URL, hash, email, and profile; the operation forwards supplied parameters to the API.
Output shape
A list of TIDE batch records, emitted as n8n items.
If the API response is not recognized as a list, the response is returned as-is and wrapped as a single output item. Errors stop execution unless the node is configured to continue on fail.