Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Login Token → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Login Token resource and the Post Undefined operation, it sends a POST request containing login token data to the Halo PSA system. This can be useful in scenarios where you need to programmatically create or update login tokens within Halo PSA, such as automating user authentication workflows, synchronizing token states, or managing session information.

Practical examples include:

  • Creating a new login token after a user logs in.
  • Updating token usage status when a token is consumed.
  • Logging token metadata like timestamps and verifiers for audit purposes.

Properties

Name Meaning
Id Numeric identifier of the login token.
Type String indicating the type/category of the login token.
Timestamp String representing the creation timestamp of the token.
Verifier String used as a verifier or validation code associated with the token.
Token The actual token string value.
Enc Id Numeric encrypted identifier related to the token.
Token Used Boolean flag indicating whether the token has been used (true/false).
Used Timestamp String timestamp marking when the token was used.
Used Userid String user ID who used the token.
Jwt JSON Web Token string associated with the login token.
Warning String field for any warning messages related to the token.

Output

The node outputs an array of JSON objects, each corresponding to one input item processed. Each output JSON object contains the response from the Halo PSA API after posting the login token data. The structure directly reflects the API's response, which typically includes confirmation of the token creation or update, along with any relevant metadata returned by the server.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Halo PSA API.
  • Needs credentials including base URL, tenant identifier, client ID, and client secret for authentication.
  • The node uses HTTP requests with appropriate headers to communicate securely with the Halo PSA service.

Troubleshooting

  • No credentials returned!
    This error occurs if the node cannot retrieve the required API credentials. Ensure that the API key credential is properly configured in n8n and assigned to the node.

  • Resource or Operation not found
    If the specified resource or operation does not exist, verify that the resource name is exactly "Login Token" and the operation is "Post Undefined". Typos or case mismatches will cause this error.

  • API request failures
    Network issues, incorrect credentials, or invalid property values may cause the API call to fail. Check the error message returned in the output JSON for details. Enabling "Continue On Fail" allows processing to continue despite errors.

  • Invalid property values
    Since many properties are sent in the request body, ensure that numeric fields receive numbers and strings are correctly formatted. Invalid types may cause the API to reject the request.

Links and References

Discussion