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
NIOS Custom API Request → Send Request
AI-generatedSummary
Sends a custom HTTP request to the NIOS WAPI endpoint you specify, using the configured NIOS credentials. The response is returned as n8n output items.
Inputs
- HTTP Method — Choose GET, DELETE, PATCH, POST, or PUT; defaults to GET.
- Endpoint (required) — NIOS WAPI path, with or without the
/wapi/vX.Yprefix, such as/record:a. - JSON Body — JSON request body for methods other than GET and DELETE; defaults to
{}. - Query Parameters — Optional name/value pairs appended as query parameters.
Output shape
One or more n8n items containing the API response data.
Array responses become one output item per element. A non-array response becomes a single item; primitive values are wrapped in a
resultfield. Request errors stop execution unless the node is configured to continue on fail, in which case an item with anerrorfield is returned.