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
DHCP Fingerprint → Create
AI-generatedSummary
Create a DHCP fingerprint in Infoblox Universal DDI by sending a POST request with the configured fields and any additional JSON body.
Inputs
- Fields (required) — Map the DHCP fingerprint fields to create. Schema fields are loaded from the Infoblox API when available; automatic mapping is supported.
- JSON Body — Optional JSON 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 additional query parameters to include with the request.
Output shape
A single record or a list of records
The API response is returned as JSON. Arrays are emitted as separate n8n items; a non-array response is emitted as one item. If Continue On Fail is enabled, request errors are returned as an item containing an error message.