Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Impersonation Request → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Impersonation Request resource and the Post Undefined operation, it sends a POST request to create or submit an impersonation request with specified details.

Typical use cases include automating the creation of impersonation requests in a service management or IT support context, where one user (the requestor) needs to act on behalf of another (the agent or user). This can be useful for audit trails, delegation, or temporary access scenarios.

For example, you might use this node to programmatically log impersonation attempts, track token usage, or manage JWT tokens related to impersonation sessions.

Properties

Name Meaning
Irid Numeric identifier for the impersonation request record.
Requestor Numeric ID of the user who is making the impersonation request.
Agent Numeric ID of the agent involved in the impersonation.
User Numeric ID of the user being impersonated.
Timestamp String timestamp indicating when the impersonation request was created.
Enc Id Numeric encrypted identifier related to the request (purpose depends on backend logic).
Token Used Boolean flag indicating whether a token has been used for this impersonation request.
Used Timestamp String timestamp indicating when the token was used.
Jwt String containing the JWT token associated with the impersonation request.
Warning String field for any warning messages related to the impersonation request.

Output

The node outputs JSON data representing the response from the Halo PSA API after submitting the impersonation request. The structure of the output JSON corresponds directly to the API's response schema for this operation, typically including confirmation details, status, or error messages.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • The node expects configuration of base URL, tenant ID, client ID, and client secret as part of the credentials.
  • Network connectivity to the Halo PSA API endpoint is necessary.

Troubleshooting

  • Missing Credentials Error: If no credentials are provided or they are invalid, the node will throw an error "No credentials returned!". Ensure that valid API authentication details are configured.
  • Resource or Operation Not Found: Errors like Resource Impersonation Request not found or Operation Post Undefined not found for resource Impersonation Request indicate misconfiguration of resource or operation names.
  • API Request Failures: Network issues, incorrect parameters, or server errors will cause the node to throw errors with messages from the API. Use the error message to diagnose issues such as invalid IDs or malformed timestamps.
  • JSON Parsing Errors: If JSON parameters are malformed, the node may fail parsing them. Validate JSON input fields carefully.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output JSON.

Links and References

Discussion