Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

NHD Identity Application → Post Undefined

AI-generated

Overview

This node integrates with the NHD Identity Application API to perform a POST operation with a customizable JSON body. It allows users to send complex structured data related to identity applications, such as redirect URIs, logout URIs, CORS whitelist entries, scopes, button configurations, authorizations, and tokens.

Typical use cases include:

  • Creating or updating identity application configurations programmatically.
  • Managing OAuth2/OpenID Connect client settings like redirect URIs and scopes.
  • Automating authorization and token management for identity applications.

For example, a user might configure this node to register a new identity application with specific redirect URIs and scopes required by their authentication system.

Properties

Name Meaning
Body A JSON object representing the payload sent in the POST request. It supports nested arrays and objects including: redirecturi_list, postlogoutredirecturi_list, cors_whitelist_list, scopes, button_config, authorizations, and tokens. Each of these fields can contain detailed configuration relevant to the identity application.

The property expects a valid JSON structure that matches the API's expected schema for an identity application.

Output

The node outputs the JSON response returned by the NHD Identity Application API after performing the POST request. The output is structured as:

{
  "json": { /* API response object */ }
}

The exact structure depends on the API response but typically includes confirmation of the created or updated identity application, including any generated IDs or status messages.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the NHD Identity Application service.
  • The node uses HTTP POST requests with JSON bodies.
  • Proper configuration of the API base URL and authentication credentials is necessary within n8n.

Troubleshooting

  • Invalid JSON Body: If the JSON provided in the Body property is malformed, the node will fail. Ensure the JSON is correctly formatted.
  • Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key or token is correctly set up.
  • API Endpoint Errors: If the API endpoint changes or the resource/operation is not supported, errors indicating "Resource not found" or "Operation not found" may occur.
  • Network Issues: Connectivity problems to the API server will result in request timeouts or connection errors.
  • Continue On Fail: If enabled, the node will return error details in the output JSON instead of stopping execution.

Links and References

Discussion