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
Endpoint Device Group → Create
AI-generatedSummary
Create a BloxOne Endpoint roaming device group by sending a POST request to Infoblox with the selected field mappings and any additional JSON body fields.
Inputs
- Fields (required) — Map the fields for the new group using the schema loaded for this resource. Fields marked required by the schema should be supplied.
- JSON Body — Optional JSON object merged over the mapped fields. Values here override mapped values with the same keys; use it for fields absent from the schema or when no schema is available.
- Query Parameters — Optional name/value query parameters appended to the request.
Output shape
A single record for the created group, or the response data returned by the API.
The response is converted into n8n output items; array responses produce one item per element. With Continue On Fail enabled, an item-level error is returned as an object containing an error message.