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 → Create
AI-generatedSummary
Create a TIDE batch by sending a POST request to Infoblox with the configured fields and any additional JSON body values. Use the field mapper for schema-supported properties, or provide fields directly in JSON when needed.
Inputs
- Fields (required) — Map the TIDE batch properties to create. The available fields are loaded from the Infoblox API schema when available; automatic mapping is supported.
- JSON Body — Optional JSON object merged over the mapped fields. Values here override mapped values with the same key; use it for fields absent from the schema or when no schema is available.
- Query Parameters — Optional additional query parameters sent with the request. TIDE filters can use parameters such as type, host, ip, URL, hash, email, or profile.
Output shape
A single record containing the API response, or one output item per element if the response is an array.
The operation submits the batch to the TIDE batches endpoint. Errors stop execution unless Continue On Fail is enabled, in which case an item containing an error message is returned.